Re: INSERT ... ON CONFLICT {UPDATE | IGNORE}

Поиск
Список
Период
Сортировка
От Peter Geoghegan
Тема Re: INSERT ... ON CONFLICT {UPDATE | IGNORE}
Дата
Msg-id CAM3SWZS4HHJFkuqPOSWe_snnrVqaF3ipFBCtZxTbC8R35scOPQ@mail.gmail.com
обсуждение исходный текст
Ответ на Re: INSERT ... ON CONFLICT {UPDATE | IGNORE}  (Robert Haas <robertmhaas@gmail.com>)
Ответы Re: INSERT ... ON CONFLICT {UPDATE | IGNORE}  (Peter Geoghegan <pg@heroku.com>)
Список pgsql-hackers
On Mon, Nov 24, 2014 at 6:26 AM, Robert Haas <robertmhaas@gmail.com> wrote:
> On Fri, Nov 21, 2014 at 3:38 PM, Peter Geoghegan <pg@heroku.com> wrote:
>> What do other people think? Should RETURNING project updated tuples as
>> well as inserted tuples, as described here?
>
> I think it should.

Looks like the consensus is that we should have RETURNING project
updated tuples too, then.

I've already written the code to do this (and to report an "UPSERT"
command tag), which is very straightforward. The next revision will
have this behavior. However, I'm going to wait a little while longer
before formally publishing a new revision.
-- 
Peter Geoghegan



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

Предыдущее
От: Thom Brown
Дата:
Сообщение: Re: postgresql.auto.conf comments
Следующее
От: Robert Haas
Дата:
Сообщение: Re: postgresql.auto.conf comments