| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
| 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 19:52:58 |
| Message-ID: | 1990141.1638388378@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
"David G. Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> writes:
> On Wed, Dec 1, 2021 at 12:21 PM Jenda Krynicky <Jenda(at)krynicky(dot)cz> wrote:
>> THERE IS NO (CENSORED) VARIABLE "Uuid"!
> Yes, there is. RETURNS TABLE (... "Uuid" text ... )
> Changing that to something else should remove the ambiguity. I agree it is
> not an ideal solution though. I'm not sure what other options exist though.
The variable_conflict options that Adrian pointed to are one way out.
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"))
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David G. Johnston | 2021-12-01 19:54:44 | Re: INSERT ... ON CONFLICT doesn't work |
| Previous Message | Tom Lane | 2021-12-01 19:49:24 | Re: case insensitive collation of Greek's sigma |