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

BUG #14327: UPSERT requires full path to column

From
egor.pugin@gmail.com
Date:
VGhlIGZvbGxvd2luZyBidWcgaGFzIGJlZW4gbG9nZ2VkIG9uIHRoZSB3ZWJz
aXRlOgoKQnVnIHJlZmVyZW5jZTogICAgICAxNDMyNwpMb2dnZWQgYnk6ICAg
ICAgICAgIEVnb3IgUHVnaW4KRW1haWwgYWRkcmVzczogICAgICBlZ29yLnB1
Z2luQGdtYWlsLmNvbQpQb3N0Z3JlU1FMIHZlcnNpb246IDkuNS40Ck9wZXJh
dGluZyBzeXN0ZW06ICAgd2luMTAKRGVzY3JpcHRpb246ICAgICAgICAKCkhp
LA0KDQpJJ3ZlIG5vdGljZWQgdXBzZXJ0IHF1ZXJ5IHdvbid0IHdvcmsgaWYg
SSBkbyBub3Qgd3JpdGUgJ3NjaGVtYS5UQUJMRS5jb2x1bW4nCmluc3RlYWQg
b2Ygc2ltcGxlICdjb2x1bW4nIGluICdvbiBjb25mbGljdCBkbyB1cGRhdGUg
c2V0JyBxdWVyeS4NCg0KV29ya2luZzoNCg0KaW5zZXJ0IGludG8gc3RhdGlz
dGljcy4iTW9zdFBvcHVsYXJEZXBlbmRlbmNpZXMiDQooaWQsIGluZGlyZWN0
LCBkb3dubG9hZHNfd2VlaykNCnZhbHVlcyAoJDEsICQyLCAxKQ0Kb24gY29u
ZmxpY3QgKGlkLCBpbmRpcmVjdCkgZG8gdXBkYXRlDQpzZXQgZG93bmxvYWRz
X3dlZWsgPSBzdGF0aXN0aWNzLiJNb3N0UG9wdWxhckRlcGVuZGVuY2llcyIu
ZG93bmxvYWRzX3dlZWsgKwoxDQp3aGVyZSBzdGF0aXN0aWNzLiJNb3N0UG9w
dWxhckRlcGVuZGVuY2llcyIuaWQgPSAkMSBhbmQKc3RhdGlzdGljcy4iTW9z
dFBvcHVsYXJEZXBlbmRlbmNpZXMiLmluZGlyZWN0ID0gJDI7DQoNCk5vdCB3
b3JraW5nOg0KDQppbnNlcnQgaW50byBzdGF0aXN0aWNzLiJNb3N0UG9wdWxh
ckRlcGVuZGVuY2llcyINCihpZCwgaW5kaXJlY3QsIGRvd25sb2Fkc193ZWVr
KQ0KdmFsdWVzICgkMSwgJDIsIDEpDQpvbiBjb25mbGljdA0KKGlkLCBpbmRp
cmVjdCkgLS0gYWxzbyB3L291dCB0aGlzLCBpdCBkb2VzIG5vdCB3b3JrIHRv
bywgYnV0IGlzbid0IGl0Cm9wdGlvbmFsIGVsZW1lbnQ/DQpkbyB1cGRhdGUN
CnNldCBkb3dubG9hZHNfd2VlayA9IGRvd25sb2Fkc193ZWVrICsgMQ0Kd2hl
cmUgaWQgPSAkMSBhbmQgaW5kaXJlY3QgPSAkMjsNCg0KCgo=

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

From
Peter Geoghegan
Date:
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

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

From
Egor Pugin
Date:
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