join (relational algebra)

{{redirect|Natural join|the SQL implementation|Natural join (SQL)}}

{{redirect|⋈|the band sometimes represented by this symbol|The Armed}}

Natural join (⨝) is a binary operator that is written as (R ⨝ S) where R and S are relations.{{efn|In Unicode, the join symbol is ⨝ (U+2A1D), and the bowtie symbol, occasionally used instead, is ⋈ (U+22C8).}} The result of the natural join is the set of all combinations of tuples in R and S that are equal on their common attribute names. For an example consider the tables Employee and Dept and their natural join:{{citation needed|date=April 2022}}

{{col-begin|width=auto; margin:0.5em auto}}

{{col-break}}

{{col-break|gap=2em}}

{{col-break|gap=2em}}

{{col-end}}

Note that neither the employee named Mary nor the Production department appear in the result. Mary does not appear in the result because Mary's Department, "Human Resources", is not listed in the Dept relation and the Production department does not appear in the result because there are no tuples in the Employee relation that have "Production" as their DeptName attribute.

This can also be used to define composition of relations. For example, the composition of Employee and Dept is their join as shown above, projected on all but the common attribute DeptName. In category theory, the join is precisely the fiber product.

The natural join is arguably one of the most important operators since it is the relational counterpart of the logical AND operator. Note that if the same variable appears in each of two predicates that are connected by AND, then that variable stands for the same thing and both appearances must always be substituted by the same value (this is a consequence of the idempotence of the logical AND). In particular, natural join allows the combination of relations that are associated by a foreign key. For example, in the above example a foreign key probably holds from Employee.DeptName to Dept.DeptName and then the natural join of Employee and Dept combines all employees with their departments. This works because the foreign key holds between attributes with the same name. If this is not the case such as in the foreign key from Dept.Manager to Employee.Name then these columns must be renamed before taking the natural join. Such a join is sometimes also referred to as an equijoin.

More formally the semantics of the natural join are defined as follows:

{{NumBlk|:|$R\; \backslash bowtie\; S\; =\; \backslash left\backslash \{\; r\; \backslash cup\; s\; \backslash \; \backslash vert\; \backslash \; r\; \backslash in\; R\; \backslash \; \backslash land\; \backslash \; s\; \backslash in\; S\; \backslash \; \backslash land\; \backslash \; \backslash mathit\{Fun\}(r\; \backslash cup\; s)\; \backslash right\backslash \}$|{{EquationRef|1}}}}

where Fun(t) is a predicate that is true for a relation t (in the mathematical sense) iff t is a function (that is, t does not map any attribute to multiple values). It is usually required that R and S must have at least one common attribute, but if this constraint is omitted, and R and S have no common attributes, then the natural join becomes exactly the Cartesian product.

The natural join can be simulated with Codd's primitives as follows. Assume that c₁,...,c_m are the attribute names common to R and S, r₁,...,r_n are the

attribute names unique to R and s₁,...,s_k are the

attribute names unique to S. Furthermore, assume that the attribute names x₁,...,x_m are neither in R nor in S. In a first step the common attribute names in S can be renamed:

{{NumBlk|:|$T\; =\; \backslash rho\_\{x\_1/c\_1,\backslash ldots,x\_m/c\_m\}(S)\; =\; \backslash rho\_\{x\_1/c\_1\}(\backslash rho\_\{x\_2/c\_2\}(\backslash ldots\backslash rho\_\{x\_m/c\_m\}(S)\backslash ldots))$|{{EquationRef|2}}}}

Then we take the Cartesian product and select the tuples that are to be joined:

{{NumBlk|:|$P\; =\; \backslash sigma\_\{c\_1=x\_1,\backslash ldots,c\_m=x\_m\}(R\; \backslash times\; T)\; =\; \backslash sigma\_\{c\_1=x\_1\}(\backslash sigma\_\{c\_2=x\_2\}(\backslash ldots\backslash sigma\_\{c\_m=x\_m\}(R\; \backslash times\; T)\backslash ldots))$|{{EquationRef|3}}}}

Finally we take a projection to get rid of the renamed attributes:

{{NumBlk|:|$U\; =\; \backslash Pi\_\{r\_1,\backslash ldots,r\_n,c\_1,\backslash ldots,c\_m,s\_1,\backslash ldots,s\_k\}(P)$|{{EquationRef|4}}}}

Consider tables Car and Boat which list models of cars and boats and their respective prices. Suppose a customer wants to buy a car and a boat, but she does not want to spend more money for the boat than for the car. The θ-join (⋈_θ) on the predicate CarPrice ≥ BoatPrice produces the flattened pairs of rows which satisfy the predicate. When using a condition where the attributes are equal, for example Price, then the condition may be specified as Price=Price

or alternatively (Price) itself.

{{col-begin|width=auto; margin:0.5em auto}}

{{col-break}}

{{col-break|gap=2em}}

{{col-break|gap=2em}}

{{col-end}}

In order to combine tuples from two relations where the combination condition is not simply the equality of shared attributes it is convenient to have a more general form of join operator, which is the θ-join (or theta-join). The θ-join is a binary operator that is written as $\{R\backslash \; \backslash bowtie\backslash \; S\; \backslash atop\; a\backslash \; \backslash theta\backslash \; b\}$ or $\{R\backslash \; \backslash bowtie\backslash \; S\; \backslash atop\; a\backslash \; \backslash theta\backslash \; v\}$ where a and b are attribute names, θ is a binary relational operator in the set {{math|1 = {<, ≤, =, ≠, >, ≥}}}, υ is a value constant, and R and S are relations. The result of this operation consists of all combinations of tuples in R and S that satisfy θ. The result of the θ-join is defined only if the headers of S and R are disjoint, that is, do not contain a common attribute.

The simulation of this operation in the fundamental operations is therefore as follows:

: R ⋈_θ S = σ_θ(R × S)

In case the operator θ is the equality operator (=) then this join is also called an equijoin.

Note, however, that a computer language that supports the natural join and selection operators does not need θ-join as well, as this can be achieved by selection from the result of a natural join (which degenerates to Cartesian product when there are no shared attributes).

In SQL implementations, joining on a predicate is usually called an inner join, and the on keyword allows one to specify the predicate used to filter the rows. It is important to note: forming the flattened Cartesian product then filtering the rows is conceptually correct, but an implementation would use more sophisticated data structures to speed up the join query.

The left semijoin (⋉ and ⋊) is a joining similar to the natural join and written as $R\; \backslash ltimes\; S$ where $R$ and $S$ are relations.{{efn|In Unicode, the ltimes symbol is ⋉ (U+22C9). The rtimes symbol is ⋊ (U+22CA)}} The result is the set of all tuples in $R$ for which there is a tuple in $S$ that is equal on their common attribute names. The difference from a natural join is that other columns of $S$ do not appear. For example, consider the tables Employee and Dept and their semijoin:{{citation needed|date=April 2022}}

{{col-begin|width=auto; margin:0.5em auto}}

{{col-break}}

{{col-break|gap=2em}}

{{col-break|gap=2em}}

{{col-end}}

More formally the semantics of the semijoin can be defined as

follows:

$R\; \backslash ltimes\; S\; =\; \backslash \{\; t\; :\; t\; \backslash in\; R\; \backslash land\; \backslash exists\; s\; \backslash in\; S(\backslash operatorname\{Fun\}(t\; \backslash cup\; s))\; \backslash \}$

where $\backslash operatorname\{Fun\}(r)$ is as in the definition of natural join.

The semijoin can be simulated using the natural join as follows. If $a\_1,\; \backslash ldots,\; a\_n$ are the attribute names of $R$, then

$R\; \backslash ltimes\; S\; =\; \backslash Pi\_\{a\_1,\; \backslash ldots,\; a\_n\}(R\; \backslash bowtie\; S).$

Since we can simulate the natural join with the basic operators it follows that this also holds for the semijoin.

In Codd's 1970 paper, semijoin is called restriction.{{cite journal|first=E.F.|last=Codd|author-link=E.F. Codd|title=A Relational Model of Data for Large Shared Data Banks|journal=Communications of the ACM|volume=13|issue=6|date=1970|pages=377–387| doi = 10.1145/362384.362685|s2cid=207549016 |doi-access=free}}

The antijoin (▷), written as R ▷ S where R and S are relations,{{efn|In Unicode, the Antijoin symbol is ▷ (U+25B7).}} is similar to the semijoin, but the result of an antijoin is only those tuples in R for which there is no tuple in S that is equal on their common attribute names.{{Cite conference |title=Unnesting Arbitrary Queries |conference=BTW |last=Neumann |first=Thomas |url=https://dl.gi.de/handle/20.500.12116/2418 |year=2015 |doi=}}

For an example consider the tables Employee and Dept and their

antijoin:

{{col-begin|width=auto; margin:0.5em auto}}

{{col-break}}

{{col-break|gap=2em}}

{{col-break|gap=2em}}

{{col-end}}

The antijoin is formally defined as follows:

: {{math|1 =R ▷ S = { t : t ∈ R ∧ ¬∃s ∈ S(Fun (t ∪ s)) }}}

or

: {{math|1 = R ▷ S = { t : t ∈ R, there is no tuple s of S that satisfies Fun (t ∪ s) }}}

where {{math|Fun (t ∪ s)}} is as in the definition of natural join.

The antijoin can also be defined as the complement of the semijoin, as follows:

{{NumBlk|:| {{math|1=R ▷ S = R − R ⋉ S}} |{{EquationRef|5}}}}

Given this, the antijoin is sometimes called the anti-semijoin, and the antijoin operator is sometimes written as semijoin symbol with a bar above it, instead of ▷.

In the case where the relations have the same attributes (union-compatible), antijoin is the same as minus.

The division (÷) is a binary operation that is written as R ÷ S. Division is not implemented directly in SQL. The result consists of the restrictions of tuples in R to the attribute names unique to R, i.e., in the header of R but not in the header of S, for which it holds that all their combinations with tuples in S are present in R.

{{col-begin|width=auto; margin:0.5em auto}}

{{col-break}}

{{col-break|gap=2em}}

{{col-break|gap=2em}}

{{col-end}}If DBProject contains all the tasks of the Database project, then the result of the division above contains exactly the students who have completed both of the tasks in the Database project.

More formally the semantics of the division is defined as follows:{{NumBlk|:| {{math|R ÷ S {{=}} { t[a₁,...,a_n] : t ∈ R ∧ ∀s ∈ S ( (t[a₁,...,a_n] ∪ s) ∈ R) } }} |{{EquationRef|6}}}}where {a₁,...,a_n} is the set of attribute names unique to R and t[a₁,...,a_n] is the restriction of t to this set. It is usually required that the attribute names in the header of S are a subset of those of R because otherwise the result of the operation will always be empty.

The simulation of the division with the basic operations is as follows. We assume that a₁,...,a_n are the attribute names unique to R and b₁,...,b_m are the attribute names of S. In the first step we project R on its unique attribute names and construct all combinations with tuples in S:

: T := π_a1,...,an(R) × S

In the prior example, T would represent a table such that every Student (because Student is the unique key / attribute of the Completed table) is combined with every given Task. So Eugene, for instance, would have two rows, Eugene → Database1 and Eugene → Database2 in T.

:: EG: First, let's pretend that "Completed" has a third attribute called "grade". It's unwanted baggage here, so we must project it off always. In fact in this step we can drop "Task" from R as well; the multiply puts it back on.

:: T := π_Student(R) × S // This gives us every possible desired combination, including those that don't actually exist in R, and excluding others (eg Fred | compiler1, which is not a desired combination)

{{col-begin|width=auto; margin:0.5em auto}}

{{col-break|gap=5em}}

{{col-end}} In the next step we subtract R from T

relation:

: U := T − R

In U we have the possible combinations that "could have" been in R, but weren't.

:: EG: Again with projections — T and R need to have identical attribute names/headers.

:: U := T − π_Student,Task(R) // This gives us a "what's missing" list.

{{col-begin|width=auto; margin:0.5em auto}}

{{col-break|gap=5em}}

{{col-break|gap=2em}}

{{col-break|gap=2em}}

{{col-end}} So if we now take the projection on the attribute names unique to R

then we have the restrictions of the tuples in R for which not

all combinations with tuples in S were present in R:

: V := π_a1,...,an(U)

:: EG: Project U down to just the attribute(s) in question (Student)

:: V := π_Student(U)

{{col-begin|width=auto; margin:0.5em auto}}

{{col-break|gap=5em}}

{{col-end}}

So what remains to be done is take the projection of R on its

unique attribute names and subtract those in V:

: W := π_a1,...,an(R) − V

:: EG: W := π_Student(R) − V.

{{col-begin|width=auto; margin:0.5em auto}}

{{col-break|gap=5em}}

{{col-break|gap=2em}}

{{col-break|gap=2em}}

{{col-end}}

{{notelist}}

{{reflist}}

Category:Relational algebra