You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For many operations, DuckDB preserves the insertion order of rows, similarly to data frame libraries such as Pandas. The following operations and components respect insertion order: The CSV reader
means: A user could be forgiven to conclude from this sentence, e.g., that aggregate functions are fed inputs in the "original table order" (see duckdb/duckdb#14755) or more generally that any arbitrarily complex and nested query on data that originates from a csv scan respects that original order, which I don't believe is the case.
I also wonder why the paragraph starts with "For many operations preserve..." and then ends with "The following operations and components respect ..: ".
It's quite unclear to me what
means: A user could be forgiven to conclude from this sentence, e.g., that aggregate functions are fed inputs in the "original table order" (see duckdb/duckdb#14755) or more generally that any arbitrarily complex and nested query on data that originates from a csv scan respects that original order, which I don't believe is the case.
I also wonder why the paragraph starts with "For many operations preserve..." and then ends with "The following operations and components respect ..: ".
Page URL: https://duckdb.org/docs/sql/dialect/order_preservation.html
The text was updated successfully, but these errors were encountered: