| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | Tim Starling <tstarling(at)wikimedia(dot)org> |
| Cc: | "pgsql-general(at)lists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Upsert error "column reference is ambiguous" |
| Date: | 2025-04-28 06:15:23 |
| Message-ID: | CAKFQuwZzU9D6vuPbWoQM7tGS8EuSoGGCUuFGJuJrhFzmCsjqUg@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Sunday, April 27, 2025, Tim Starling <tstarling(at)wikimedia(dot)org> wrote:
> thus allowing it to DWIM.
We intentionally choose (or, in any case have established) a SWYM approach
here.
Personally I’d be fine with the reduced helpfulness in trying to prevent
buggy queries in the interest of being more conforming with the broader
world. I am curious as to whether we are in strict adherence to the SQL
Standard on this point though. Makes deviation a bit tougher to justify.
It does seem that project policies would prevent back-patching such a
change.
David J.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | KK CHN | 2025-04-28 06:23:21 | pgbackrest with two remote backend servers fails |
| Previous Message | Tim Starling | 2025-04-28 04:55:58 | Upsert error "column reference is ambiguous" |