Re: BUG #14327: UPSERT requires full path to column - Mailing list pgsql-bugs

From Peter Geoghegan
Subject Re: BUG #14327: UPSERT requires full path to column
Date
Msg-id CAM3SWZTS10xLUxOHKa-t7E-K7L7LOE2Ag4WFm-mUYOGNH1UXEQ@mail.gmail.com
Whole thread Raw
In response to BUG #14327: UPSERT requires full path to column  (egor.pugin@gmail.com)
Responses Re: BUG #14327: UPSERT requires full path to column  (Egor Pugin <egor.pugin@gmail.com>)
List pgsql-bugs
On Mon, Sep 19, 2016 at 1:06 AM,  <egor.pugin@gmail.com> wrote:
> I've noticed upsert query won't work if I do not write 'schema.TABLE.column'
> instead of simple 'column' in 'on conflict do update set' query.

Use an alias. e.g.:

INSERT INTO statistics."MostPopularDependencies" as mpd ...

You can then reference columns using mpd.downloads_week, etc

--
Peter Geoghegan

pgsql-bugs by date:

Previous
From: egor.pugin@gmail.com
Date:
Subject: BUG #14327: UPSERT requires full path to column
Next
From: Egor Pugin
Date:
Subject: Re: BUG #14327: UPSERT requires full path to column