From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Jenda Krynicky <Jenda(at)krynicky(dot)cz>, "pgsql-generallists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org> |
Subject: | Re: INSERT ... ON CONFLICT doesn't work |
Date: | 2021-12-01 20:04:07 |
Message-ID: | CAKFQuwaZ=Jfw0bJDiJTzqXSAR+PvVZC7hpJcXCe8ke8mqzEG1A@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Wed, Dec 1, 2021 at 12:59 PM David G. Johnston <
david(dot)g(dot)johnston(at)gmail(dot)com> wrote:
> On Wed, Dec 1, 2021 at 12:52 PM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>
>> It's also possible to qualify the name in the ON CONFLICT clause,
>> although I think you have to parenthesize it to do so:
>>
>> ... ON CONFLICT (("Lockers"."Uuid"))
>>
>>
> This really needs to be confirmed and, if so, better documented on the
> INSERT page, since adding a schema to the index_column_name does not
> intuitively turn it into an index_expression which is what the syntax
> diagram says requires an extra pair of parentheses.
>
>
That of course should be adding a table qualifier to the column, not a
schema qualifier. I get why INSERT doesn't really care, the source table
is never in question in SQL-land, but as we see here there is a valid need
for it in plpgsql.
David J.
From | Date | Subject | |
---|---|---|---|
Next Message | Jenda Krynicky | 2021-12-01 20:04:27 | Re: INSERT ... ON CONFLICT doesn't work |
Previous Message | David G. Johnston | 2021-12-01 19:59:17 | Re: INSERT ... ON CONFLICT doesn't work |