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-20T17:59:18Z
Lists: pgsql-hackers
James Coleman <jtc331@gmail.com> writes: > I do wonder if it's plausible (and sufficiently easy) to improve the > error message here. "column 'foo' of relation 'foo'" makes one thing > that you've written foo.foo, (in my real-world case the error message > also cut off the sql past "foo.", and so I couldn't even tell if the > sql was just malformed). At the very least it'd be nice to have a HINT > here (perhaps just when the relation and column name match). > Before I look at where it is, Is such an improvement something we'd be > interested in? 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. regards, tom lane
Commits
-
Add hint about not qualifying UPDATE...SET target with relation name.
- 58447e31890a 17.0 landed