Re: PG12 change to DO UPDATE SET column references
| От | David G. Johnston |
|---|---|
| Тема | Re: PG12 change to DO UPDATE SET column references |
| Дата | |
| Msg-id | CAKFQuwYLNDzj1+kvig03hLiaj6SmWu-Fxc5oU+cQBL+-+7tsiw@mail.gmail.com обсуждение исходный текст |
| Ответ на | PG12 change to DO UPDATE SET column references (James Coleman <jtc331@gmail.com>) |
| Ответы |
Re: PG12 change to DO UPDATE SET column references
|
| Список | pgsql-hackers |
On Fri, Jan 19, 2024 at 10:01 AM James Coleman <jtc331@gmail.com> wrote:
Making this more confusing is the fact that if I want to do something
like "SET bar = foo.bar + 1" the table qualification cannot be present
on the setting column but is required on the reading column.
There isn't anything in the docs that I see about this, and I don't
see anything scanning the release notes for PG12 either (though I
could have missed a keyword to search for).
"When referencing a column with ON CONFLICT DO UPDATE, do not include the table's name in the specification of a target column. For example, INSERT INTO table_name ... ON CONFLICT DO UPDATE SET table_name.col = 1 is invalid (this follows the general behavior for UPDATE)."
The same text exists for v11.
David J.
В списке pgsql-hackers по дате отправления: