Re: BUG #14327: UPSERT requires full path to column

Поиск
Список
Период
Сортировка
От Egor Pugin
Тема Re: BUG #14327: UPSERT requires full path to column
Дата
Msg-id CAHtU+mpT22XCe5f5smYQgSHfhi5-5aGW91re1sGXDeB5R7q6ag@mail.gmail.com
обсуждение исходный текст
Ответ на Re: BUG #14327: UPSERT requires full path to column  (Peter Geoghegan <pg@heroku.com>)
Список pgsql-bugs
Thanks!
But is this expected behavior and not a bug?

On 19 September 2016 at 13:06, Peter Geoghegan <pg@heroku.com> wrote:
> 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



--
Egor Pugin

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

Предыдущее
От: Peter Geoghegan
Дата:
Сообщение: Re: BUG #14327: UPSERT requires full path to column
Следующее
От: Huan Ruan
Дата:
Сообщение: Re: BUG #14319: Logical decoding dropping statements in subtransactions