Re: INSERT ... ON CONFLICT syntax issues

Поиск
Список
Период
Сортировка
От Peter Geoghegan
Тема Re: INSERT ... ON CONFLICT syntax issues
Дата
Msg-id CAM3SWZQYomh8u+3zVb9fOXyiTY=_G6sEQFuR5LEM5dp2A6Baig@mail.gmail.com
обсуждение исходный текст
Ответ на Re: INSERT ... ON CONFLICT syntax issues  ("David G. Johnston" <david.g.johnston@gmail.com>)
Список pgsql-hackers
On Tue, Apr 28, 2015 at 10:36 AM, David G. Johnston
<david.g.johnston@gmail.com> wrote:
> This example exemplifies the poorness of the proposed wording, IMO:
>
>
> [...]
> SET dname = EXCLUDED.dname || ' (formerly ' || TARGET.dname || ')'
>
> NEW.dname || '(formerly ' || OLD.dname || ')' reads perfectly well.
>
> Yes, this is an isolated example...but am I missing the fact that there is a
> third tuple that needs to be referenced?
>
> If there are only two the choices of NEW and OLD seem to be both easily
> learned and readable.

Whatever Andres and/or Heikki want is what I'll agree to. Honestly, I
just don't care anymore.


-- 
Peter Geoghegan



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

Предыдущее
От: Tom Lane
Дата:
Сообщение: Re: ATSimpleRecursion() and inheritance foreign parents
Следующее
От: Merlin Moncure
Дата:
Сообщение: Re: cache invalidation for PL/pgsql functions