Re: Incorrect UPDATE trigger invocation in the UPDATE clause of an UPSERT statement.

Поиск
Список
Период
Сортировка
От Michael Paquier
Тема Re: Incorrect UPDATE trigger invocation in the UPDATE clause of an UPSERT statement.
Дата
Msg-id CAB7nPqTjO4decSSm2DxeUrchX10SJ3GfKTddgBH42bvX5k4WjQ@mail.gmail.com
обсуждение исходный текст
Ответ на Incorrect UPDATE trigger invocation in the UPDATE clause of an UPSERT statement.  (Stanislav Grozev <tacho@daemonz.org>)
Ответы Re: Incorrect UPDATE trigger invocation in the UPDATE clause of an UPSERT statement.  (Stanislav Grozev <tacho@daemonz.org>)
Re: Incorrect UPDATE trigger invocation in the UPDATE clause of an UPSERT statement.  (Dean Rasheed <dean.a.rasheed@gmail.com>)
Список pgsql-bugs
Дерево обсуждения 
On Mon, Nov 30, 2015 at 8:43 PM, Stanislav Grozev wrote:
> If we do an UPSERT instead, watch how OLD and NEW are the same (NEW):

AFAIK, that's the expected behavior. AFTER UPDATE triggers firing for
ON CONFLICT DO UPDATE will see the same NEW and OLD values. Comments
from others?
--
Michael

В списке pgsql-bugs по дате отправления:

Предыдущее
От: Paul Moore
Дата:
Сообщение: Re: BUG #13788: compile error in generic_msvc.h
Следующее
От: Stanislav Grozev
Дата:
Сообщение: Re: Incorrect UPDATE trigger invocation in the UPDATE clause of an UPSERT statement.