| From: | Daniel Gustafsson <daniel(at)yesql(dot)se> |
|---|---|
| To: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>, Vik Fearing <vik(dot)fearing(at)2ndquadrant(dot)com> |
| Cc: | Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Allow an alias to be attached directly to a JOIN ... USING |
| Date: | 2020-07-09 11:38:45 |
| Message-ID: | AC332529-08F3-4FC6-BD31-C375A64DF305@yesql.se |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> On 27 Jan 2020, at 10:19, Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> wrote:
>
> On 2019-12-31 00:07, Vik Fearing wrote:
>> One thing I notice is that the joined columns are still accessible from
>> their respective table names when they should not be per spec. That
>> might be one of those "silly restrictions" that we choose to ignore, but
>> it should probably be noted somewhere, at the very least in a code
>> comment if not in user documentation. (This is my reading of SQL:2016 SR
>> 11.a.i)
>
> Here is a rebased patch.
This thread has stalled for a bit, let's try to bring it to an end.
Vik: having shown interest in, and been actively reviewing, this patch; do you
have time to review this latest version from Peter during this commitfest?
cheers ./daniel
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Petr Jelinek | 2020-07-09 11:45:58 | Re: replication_origin and replication_origin_lsn usage on subscriber |
| Previous Message | Daniel Gustafsson | 2020-07-09 11:25:43 | Re: Log the location field before any backtrace |