Skip to content

Commit 7bc79d9

Browse files
Merge pull request #215 from Trivadis/feature/issue-209-g-3182-column-alias
include column alias in title and reason of G-3182
2 parents e66783b + 7d5345a commit 7bc79d9

File tree

1 file changed

+2
-2
lines changed
  • docs/4-language-usage/3-dml-and-sql/1-general

1 file changed

+2
-2
lines changed

Diff for: docs/4-language-usage/3-dml-and-sql/1-general/g-3182.md

+2-2
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,4 @@
1-
# G-3182: Always specify column names instead of positional references in GROUP BY clauses.
1+
# G-3182: Always specify column names/aliases instead of positional references in GROUP BY clauses.
22

33
!!! bug "Blocker"
44
Reliability
@@ -11,7 +11,7 @@ Oracle Database 23c
1111

1212
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.
1313

14-
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.
14+
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.
1515

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

0 commit comments

Comments
 (0)