Re: INSERT ... ON CONFLICT syntax issues
От
Geoff Winkless
Тема
Re: INSERT ... ON CONFLICT syntax issues
Дата
Msg-id
CAEzk6ffVmfF8bY=6+LvTwe6i1ZAwVoCManBzHhDGEjsNQ0E5pA@mail.gmail.com
Ответ на
Re: INSERT ... ON CONFLICT syntax issues (Heikki Linnakangas)
Список
Дерево обсуждения
INSERT ... ON CONFLICT syntax issues Andres Freund <andres@anarazel.de>
Re: INSERT ... ON CONFLICT syntax issues Peter Geoghegan <pg@heroku.com>
Re: INSERT ... ON CONFLICT syntax issues Andres Freund <andres@anarazel.de>
Re: INSERT ... ON CONFLICT syntax issues Peter Geoghegan <pg@heroku.com>
Re: INSERT ... ON CONFLICT syntax issues Andres Freund <andres@anarazel.de>
Re: INSERT ... ON CONFLICT syntax issues Peter Geoghegan <pg@heroku.com>
Re: INSERT ... ON CONFLICT syntax issues Peter Geoghegan <pg@heroku.com>
Re: INSERT ... ON CONFLICT syntax issues Peter Geoghegan <pg@heroku.com>
Re: INSERT ... ON CONFLICT syntax issues Peter Eisentraut <peter_e@gmx.net>
Re: INSERT ... ON CONFLICT syntax issues Peter Geoghegan <pg@heroku.com>
Re: INSERT ... ON CONFLICT syntax issues Simon Riggs <simon@2ndQuadrant.com>
Re: INSERT ... ON CONFLICT syntax issues Peter Geoghegan <pg@heroku.com>
On 05/07/2015 12:01 AM, Andres Freund wrote:On 2015-05-06 23:48:18 +0300, Heikki Linnakangas wrote:I'll see about fixing that. It's not just a matter of creating another alias
for the same rel, I'm afraid: "foo.t" is supposed to refer to the tuple that
we attempted to insert, like it does without the ON CONFLICT.
I'm not sure what you mean here?
Sorry, forget about that. I was confused and mixed up EXCLUDED and TARGET. Looks like they really aren't very good names :-).
Could
INSERT.column and
CONFLICT.column work? So INSERT is the row that you were inserting, and CONFLICT is the row with which it conflicted?
Geoff
В списке pgsql-hackers по дате отправления
