Skip to content

include column alias in title and reason of G-3182 #215

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.

Sign up for GitHub

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

Merged
merged 1 commit into from
Mar 13, 2024
Merged

include column alias in title and reason of G-3182 #215

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions docs/4-language-usage/3-dml-and-sql/1-general/g-3182.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,4 +1,4 @@
# G-3182: Always specify column names instead of positional references in GROUP BY clauses.
# G-3182: Always specify column names/aliases instead of positional references in GROUP BY clauses.

!!! bug "Blocker"
Reliability
Expand All @@ -11,7 +11,7 @@ Oracle Database 23c

If you use a numeric literal in the `group by` clause in an Oracle Database prior to version 23c, then this literal is not required. It is simply a constant.

Starting with Oracle Database 23c, it is possible to use a literal in the `group by` clause to refer to a column name in the `select` list. However, this only works if the `group_by_position_enabled` parameter is set to `true`. In any case, it is not convenient for the readers of the code to have to count the columns in the `select` list to know how the result is grouped.
Starting with Oracle Database 23c, it is possible to use a literal in the `group by` clause to refer to a column name or column alias in the `select` list. However, this only works if the `group_by_position_enabled` parameter is set to `true`. In any case, it is not convenient for the readers of the code to have to count the columns in the `select` list to know how the result is grouped.

Since the meaning of a `literal` depends on the configuration and database version, the intention is unclear and might lead to an incorrect result.

Expand Down