Show result columns in select-list order - #7
Merged
Merged
Conversation
Rows are maps, so the TUI and CLI used to put the columns in alphabetical order (the TUI put id first). `select name, count(*), id` came back as count(*), id, name. The planner now records the select list's output columns on the plan (Plan.columns), after removing duplicates. Grouped queries record their output names. Both result views use that order: the TUI table, the TUI row inspector, and the CLI's Owl table through its sort_columns option. A selected field missing from a row shows as null in the CLI instead of dropping its column. `select *` has no select list, so it keeps the old order. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01PFBZUrerge6bbWVCHpS5Ko
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Rows are maps, so the TUI and CLI used to put the columns in alphabetical
order (the TUI put id first).
select name, count(*), idcame back ascount(*), id, name.
The planner now records the select list's output columns on the plan
(Plan.columns), after removing duplicates. Grouped queries record their
output names. Both result views use that order: the TUI table, the TUI row
inspector, and the CLI's Owl table through its sort_columns option. A
selected field missing from a row shows as null in the CLI instead of
dropping its column.
select *has no select list, so it keeps the oldorder.
Co-Authored-By: Claude Opus 5.5 noreply@anthropic.com
Claude-Session: https://claude.ai/code/session_01PFBZUrerge6bbWVCHpS5Ko