From 3fd5decc542b7677a5ad6a8bf73c91b3da9c9525 Mon Sep 17 00:00:00 2001 From: Gabor Szarnyas Date: Thu, 9 Jan 2025 15:45:14 +0100 Subject: [PATCH] Add comment on order preservation --- _posts/2025-01-09-union-by-name.md | 1 + 1 file changed, 1 insertion(+) diff --git a/_posts/2025-01-09-union-by-name.md b/_posts/2025-01-09-union-by-name.md index 9652f403fbc..b154234e4c6 100644 --- a/_posts/2025-01-09-union-by-name.md +++ b/_posts/2025-01-09-union-by-name.md @@ -90,6 +90,7 @@ Unfortunately we have Codd to thank for this confusing bit! If only `UNION ALL` were the default... Typically, `UNION ALL` (and its new counterpart `UNION ALL BY NAME`!) are the desired behavior as they faithfully reproduce the input relations, just stacked together. This is higher performance as well, since the deduplication that occurs with `UNION` can be quite time intensive with large datasets. +And finally, `UNION ALL` is [preserves the original row order]({% link docs/sql/dialect/order_preservation.md %}). ### Reading Multiple Files