fix: SQL interface "off-by-one' indexing error with GROUP BY
clauses that use position ordinals
#15584
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.
Closes #14704.
We already had all the machinery in place for handling "GROUP BY" clauses1 that use ordinal position values, but were defeated by a classic "off by one" error (as SQL is 1-indexed). Fixed it and added the missing test coverage. Will look at adding support for ordinal position values in "ORDER BY" clauses separately.
(Having ordinal position values in both clauses is supported by standard PostgreSQL syntax).
Example
Footnotes
https://www.postgresql.org/docs/current/sql-select.html#SQL-GROUPBY ↩