Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Issue found on page 'Order Preservation' #4035

Open
soerenwolfers opened this issue Nov 9, 2024 · 0 comments
Open

Issue found on page 'Order Preservation' #4035

soerenwolfers opened this issue Nov 9, 2024 · 0 comments

Comments

@soerenwolfers
Copy link
Contributor

It's quite unclear to me what

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 ..: ".

Page URL: https://duckdb.org/docs/sql/dialect/order_preservation.html

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant