Re: INSERT ... ON CONFLICT DO UPDATE with _any_ constraint

Поиск
Список
Период
Сортировка
От Stephen Frost
Тема Re: INSERT ... ON CONFLICT DO UPDATE with _any_ constraint
Дата
Msg-id 20150521193527.GV26667@tamriel.snowman.net
обсуждение исходный текст
Ответ на Re: INSERT ... ON CONFLICT DO UPDATE with _any_ constraint  (Simon Riggs <simon@2ndQuadrant.com>)
Список pgsql-hackers
* Simon Riggs (simon@2ndQuadrant.com) wrote:
> On 21 May 2015 at 14:25, Peter Geoghegan <pg@heroku.com> wrote:
> > > If the update is the same no matter which constraint is violated, why
> > would
> > > I need to specify the constraint? We're forcing the developer to make an
> > > arbitrary choice between two constraints.
> >
> > Why would the update be the same, though?
>
> *If* is the keyword there.

Agreed.

> > We will see many people ask why they have to specify constraints
> > explicitly.
> >
> > I'm not sure that we will, actually, but as I said, go ahead and
> > propose removing the restriction if you think it's important (maybe
> > start a thread on it).
> >
>
> I am. I have. Many times. What is wrong with this thread or all of the
> other times I said it?
>
> Please look at the $SUBJECT of this thread. We're here now.

I've also asked for this.
Thanks!
    Stephen

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

Предыдущее
От: Tom Lane
Дата:
Сообщение: Re: Fix misaligned access of ItemPointerData on ARM
Следующее
От: Michael Meskes
Дата:
Сообщение: Re: Problems with question marks in operators (JDBC, ECPG, ...)