8000
We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
There was an error while loading. Please reload this page.
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
https://duckdb.org/docs/stable/sql/dialect/order_preservation.html says that the prefer of results is preserved with where clauses. But this does not work when there is an or in the query.
or
CREATE TABLE tbl AS SELECT * FROM (VALUES (1, 'a'), (2, 'b'), (3, 'c')) t(x, y); SELECT * FROM tbl;
select * from tbl where y = 'b' or y = 'a';
Results in
┌───────┬─────────┐ │ x │ y │ │ int32 │ varchar │ ├───────┼─────────┤ │ 2 │ b │ │ 1 │ a │ └───────┴─────────┘
when it should be
┌───────┬─────────┐ │ x │ y │ │ int32 │ varchar │ ├───────┼─────────┤ │ 1 │ a │ │ 2 │ b │ └───────┴─────────┘
macOS
v1.2.2 7c03946
CLI
No response
Dominik Moritz
CMU
I have tested with a stable release
Yes
The text was updated successfully, but these errors were encountered:
Successfully merging a pull request may close this issue.
What happens?
https://duckdb.org/docs/stable/sql/dialect/order_preservation.html says that the prefer of results is preserved with where clauses. But this does not work when there is an
or
in the query.To Reproduce
Results in
when it should be
OS:
macOS
DuckDB Version:
v1.2.2 7c03946
DuckDB Client:
CLI
Hardware:
No response
Full Name:
Dominik Moritz
Affiliation:
CMU
What is the latest build you tested with? If possible, we recommend testing with the latest nightly build.
I have tested with a stable release
Did you include all relevant data sets for reproducing the issue?
Yes
Did you include all code required to reproduce the issue?
Did you include all relevant configuration (e.g., CPU architecture, Python version, Linux distribution) to reproduce the issue?
The text was updated successfully, but these errors were encountered: