hcq/postgresql
1
0
Fork 0
mirror of https://git.postgresql.org/git/postgresql.git synced 2026-02-16 03:17:00 +08:00
Code Issues Packages Projects Releases Wiki Activity

Make subquery aliases optional in the FROM clause.

Browse Source 
This allows aliases for sub-SELECTs and VALUES clauses in the FROM
clause to be omitted.

This is an extension of the SQL standard, supported by some other
database systems, and so eases the transition from such systems, as
well as removing the minor inconvenience caused by requiring these
aliases.

Patch by me, reviewed by Tom Lane.

Discussion: https://postgr.es/m/CAEZATCUCGCf82=hxd9N5n6xGHPyYpQnxW8HneeH+uP7yNALkWA@mail.gmail.com
This commit is contained in:
Dean Rasheed
2022-07-20 09:29:42 +01:00
parent 1caf915ff3
commit bcedd8f5fc
10 changed files with 164 additions and 81 deletions
Download Patch File Download Diff File Expand all files Collapse all files

7
src/include/parser/parse_node.h
View File

@ -246,8 +246,11 @@ struct ParseState
* visible for qualified references) but it does hide their columns
* (unqualified references to the columns refer to the JOIN, not the member
* tables, so we must not complain that such a reference is ambiguous).
* Various special RTEs such as NEW/OLD for rules may also appear with only
* one flag set.
* Conversely, a subquery without an alias does not hide the columns selected
* by the subquery, but it does hide the auto-generated relation name (so the
* subquery columns are visible for unqualified references only). Various
* special RTEs such as NEW/OLD for rules may also appear with only one flag
* set.
*
* While processing the FROM clause, namespace items may appear with
* p_lateral_only set, meaning they are visible only to LATERAL