This commit is contained in:
@@ -1 +1,6 @@
|
||||
---
|
||||
note type: note
|
||||
date: 2026-06-03
|
||||
done: true
|
||||
---
|
||||
A DAG (short for directed acyclic graphs) is a model that encapsulates everything needed to execute a workflow. [See this](https://airflow.apache.org/docs/apache-airflow/stable/core-concepts/dags.html)
|
||||
|
||||
@@ -1,3 +1,10 @@
|
||||
---
|
||||
note type:
|
||||
- note
|
||||
- database
|
||||
date: 2026-06-03
|
||||
done: true
|
||||
---
|
||||
A task in the context of airflow is the basic unit of execution. They are arranged into [[Airflow Dags]] and then have upstream and downstream dependencies set between them in order to express the order in which they should be run.
|
||||
|
||||
There are three kinds of tasks:
|
||||
|
||||
@@ -1,3 +1,8 @@
|
||||
---
|
||||
note type: database
|
||||
date: 2026-06-03
|
||||
done: true
|
||||
---
|
||||
# xcom
|
||||
|
||||
XComs stands for cross-communications, and as the name suggests, it allows [[Airflow Tasks]] to talk to each other (because by default, tasks are entirely isolated and can run on seperate machines).
|
||||
|
||||
@@ -1,2 +1,9 @@
|
||||
---
|
||||
note type:
|
||||
- moc
|
||||
- database
|
||||
date: 2026-06-03
|
||||
done: true
|
||||
---
|
||||
- [[Postgres]]
|
||||
- [[Airflow]]
|
||||
|
||||
@@ -1,3 +1,10 @@
|
||||
---
|
||||
note type:
|
||||
- database
|
||||
- note
|
||||
date: 2026-06-03
|
||||
done: true
|
||||
---
|
||||
# Introduction
|
||||
|
||||
Database security is a crucial part of database administration. It ensures that only authorised users can access, modify, or manage data. Three core concepts used to control access are:
|
||||
|
||||
@@ -1,3 +1,10 @@
|
||||
---
|
||||
note type:
|
||||
- database
|
||||
- note
|
||||
date: 2026-06-03
|
||||
done: true
|
||||
---
|
||||
``` bash
|
||||
psql -h 82.18.104.48 -p 5432 -U zaine -d org_web
|
||||
```
|
||||
|
||||
@@ -1,10 +1,18 @@
|
||||
---
|
||||
note type:
|
||||
- database
|
||||
- theory
|
||||
date: 2026-06-03
|
||||
done:
|
||||
---
|
||||
|
||||
# The SQL JOIN Clause
|
||||
|
||||
The JOIN clause is used to combine rows from two or more tables, based on a related column between them.
|
||||
|
||||
Here are the different types of JOINs in SQL:
|
||||
|
||||
****(INNER) JOIN****: Returns only rows that have matching values in both tables
|
||||
****LEFT (OUTER) JOIN****: Returns all rows from the left table, and only the matched rows from the right table
|
||||
****RIGHT (OUTER) JOIN****: Returns all rows from the right table, and only the matched rows from the left table
|
||||
****FULL (OUTER) JOIN****: Returns all rows when there is a match in either the left or right table
|
||||
- (INNER) JOIN: Returns only rows that have matching values in both tables
|
||||
- LEFT (OUTER) JOIN: Returns all rows from the left table, and only the matched rows from the right table
|
||||
- RIGHT (OUTER) JOIN: Returns all rows from the right table, and only the matched rows from the left table
|
||||
- FULL (OUTER) JOIN: Returns all rows when there is a match in either the left or right table
|
||||
|
||||
Reference in New Issue
Block a user