Skip to content

Commit

Permalink
nit
Browse files Browse the repository at this point in the history
  • Loading branch information
szarnyasg committed Jan 9, 2025
1 parent 3fd5dec commit ee33f84
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion _posts/2025-01-09-union-by-name.md
Original file line number Diff line number Diff line change
Expand Up @@ -46,7 +46,7 @@ Fast forward just a couple of decades, and DuckDB is making stacking in SQL tota

## Making Vertical Stacking Groovy Again

In addition to the traditional [`UNION`]({% link docs/sql/query_syntax/setops.md %}#union) and [`UNION ALL`]({% link docs/sql/query_syntax/setops.md %}#union-all-bag-semantics) operators, DuckDB adds both [`UNION BY NAME` and `UNION ALL BY NAME`]({% link docs/sql/query_syntax/setops.html %}#union-all-by-name).
In addition to the traditional [`UNION`]({% link docs/sql/query_syntax/setops.md %}#union) and [`UNION ALL`]({% link docs/sql/query_syntax/setops.md %}#union-all-bag-semantics) operators, DuckDB adds both [`UNION BY NAME` and `UNION ALL BY NAME`]({% link docs/sql/query_syntax/setops.md %}#union-all-by-name).
These will vertically stack multiple relations (e.g., `SELECT` statements) by matching on the names of columns independent of their order.
As an example, we provide columns `a` and `b` out of order, and even introduce the entirely new column `c` and stacking will still succeed:

Expand Down

0 comments on commit ee33f84

Please sign in to comment.