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

ORDER BY with nested list type gives wrong result #11936

Closed
2 tasks
gitccl opened this issue May 5, 2024 · 0 comments · Fixed by #11937
Closed
2 tasks

ORDER BY with nested list type gives wrong result #11936

gitccl opened this issue May 5, 2024 · 0 comments · Fixed by #11937
Labels
PR submitted A pull request was submitted to fix the issue

Comments

@gitccl
Copy link
Contributor

gitccl commented May 5, 2024

What happens?

ORDER BY with nested list type gives wrong result.

To Reproduce

CREATE TABLE test(col1 INT, col2 INT2[][][][][][]);
INSERT INTO test VALUES(1000000000, null), (1000000001, [[[[[[]]]]]]), (null, [[[[[[]]]]]]), (null, [[[[[[]]]]]]), (1, [[[[[[]]]]]]);
SELECT col1, col2 FROM test ORDER BY col1 NULLS LAST, col2;
┌────────────┬───────────────────┐
│    col1    │       col2        │
│   int32    │ int16[][][][][][] │
├────────────┼───────────────────┤
│            │ [[[[[[]]]]]]      │
│            │ [[[[[[]]]]]]      │
│          1 │ [[[[[[]]]]]]      │
│ 1000000000 │                   │
│ 1000000001 │ [[[[[[]]]]]]      │
└────────────┴───────────────────┘

OS:

x64

DuckDB Version:

main

DuckDB Client:

cmd

Full Name:

gitccl

Affiliation:

Zhejiang University

What is the latest build you tested with? If possible, we recommend testing with the latest nightly build.

I have tested with a source build

Did you include all relevant data sets for reproducing the issue?

Yes

Did you include all code required to reproduce the issue?

  • Yes, I have

Did you include all relevant configuration (e.g., CPU architecture, Python version, Linux distribution) to reproduce the issue?

  • Yes, I have
@szarnyasg szarnyasg added the PR submitted A pull request was submitted to fix the issue label May 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
PR submitted A pull request was submitted to fix the issue
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants