| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Rob McColl <rob(at)robmccoll(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: PostgreSQL 10 parenthesized single-column updates can produce errors |
| Date: | 2017-10-31 22:48:39 |
| Message-ID: | CAKFQuwZYvtyBXYey=smWfEUUEF6-1Y5CAm4vDbDY3MMFzK8_OQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Oct 31, 2017 at 3:43 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> According to the spec, the elements of a parenthesized
> SET list should be assigned from the fields of a composite RHS. If
> there's just one element of the SET list, the RHS should be a single-field
> composite value, and this syntax should result in extracting its field.
> This patch doesn't do that; it preserves our previous broken behavior,
> and thus just puts off the day of reckoning that inevitably will come.
>
Definitely moderates my opinion in my concurrent email...though
postponement is not strictly bad given the seeming frequency of the
existing problematic syntax in the wild already.
David J.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Gilles Darold | 2017-10-31 23:02:26 | Re: proposal: schema variables |
| Previous Message | David G. Johnston | 2017-10-31 22:45:28 | Re: PostgreSQL 10 parenthesized single-column updates can produce errors |