Re: PG12 change to DO UPDATE SET column references
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: James Coleman <jtc331@gmail.com>
Cc: pgsql-hackers <pgsql-hackers@postgresql.org>
Date: 2024-01-20T22:57:46Z
Lists: pgsql-hackers
James Coleman <jtc331@gmail.com> writes: > On Sat, Jan 20, 2024 at 12:59 PM Tom Lane <tgl@sss.pgh.pa.us> wrote: >> A HINT if the bogus column name (1) matches the relation name and >> (2) is field-qualified seems plausible to me. Then it's pretty >> likely to be a user misunderstanding about whether to write the >> relation name. > Attached is a patch to do just that. We could also add tests for > regular UPDATEs if you think that's useful. Pushed with minor alterations: 1. I think our usual style for conditional hints is to use a ternary expression within the ereport, rather than duplicating code. In this case that way allows not touching any of the existing lines, making review easier. 2. I thought we should test the UPDATE case as well as the ON CONFLICT case, but I didn't think we needed quite as many tests as you had here. I split up the responsibility so that one test covers the alias case and the other the no-alias case. regards, tom lane
Commits
-
Add hint about not qualifying UPDATE...SET target with relation name.
- 58447e31890a 17.0 landed