Skip to content

Commit

Permalink
Merge pull request #215 from Trivadis/feature/issue-209-g-3182-column…
Browse files Browse the repository at this point in the history
…-alias

include column alias in title and reason of G-3182
  • Loading branch information
PhilippSalvisberg committed Mar 13, 2024
2 parents e66783b + 7d5345a commit 7bc79d9
Showing 1 changed file with 2 additions and 2 deletions.
4 changes: 2 additions & 2 deletions docs/4-language-usage/3-dml-and-sql/1-general/g-3182.md
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

0 comments on commit 7bc79d9

Please sign in to comment.