| From: | Kirill Reshke <reshkekirill(at)gmail(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Peter Eisentraut <peter(at)eisentraut(dot)org>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Allow subfield references without parentheses |
| Date: | 2024-12-13 04:26:21 |
| Message-ID: | CALdSSPjf4dsEckp+O2t0e4Lms8DHP+UxQmOfRTcaaNOQmhJ8mQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, 12 Dec 2024, 21:45 Tom Lane, <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Peter Eisentraut <peter(at)eisentraut(dot)org> writes:
> > This patch allows subfield references in column references without
> > parentheses, subject to certain condition. This implements (hopes to,
> > anyway) the rules from the SQL standard (since SQL99).
> > This has been requested a number of times over the years. [0] is a
> > recent discussion that has mentioned it.
>
> The obvious concern about this is introduction of ambiguity where
> there was none before.
>
IMHO SQL standard compatibility is a more compelling argument here.
>
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Hunaid Sohail | 2024-12-13 04:47:51 | Re: Psql meta-command conninfo+ |
| Previous Message | Sutou Kouhei | 2024-12-13 03:27:37 | Re: confusing / inefficient "need_transcoding" handling in copy |