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

Fix ordering issue with nested list type #11937

Merged
merged 1 commit into from May 13, 2024
Merged

Conversation

gitccl
Copy link
Contributor

@gitccl gitccl commented May 5, 2024

Fixes #11936 .
Back to the code, we have used two bytes, one to indicate whether it is null, and the other to indicate whether the list is empty, so here is width - 2 instead of width - 1.

@szarnyasg szarnyasg requested a review from lnkuiper May 5, 2024 17:46
Copy link
Contributor

@lnkuiper lnkuiper left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good catch, thanks! LGTM

@gitccl
Copy link
Contributor Author

gitccl commented May 13, 2024

There seems to be a test that failed because of the network.

@Mytherin Mytherin merged commit d4c6e67 into duckdb:main May 13, 2024
41 checks passed
@Mytherin
Copy link
Collaborator

Thanks!

github-actions bot pushed a commit to duckdb/duckdb-r that referenced this pull request May 13, 2024
@gitccl gitccl deleted the fix_orderby branch May 14, 2024 02:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

ORDER BY with nested list type gives wrong result
3 participants