Re: INSERT ... ON CONFLICT doesn't work

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
> "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
>

ERROR: invalid reference to FROM-clause entry for table "Lockers"
LINE 3: ON CONFLICT (("Lockers"."Uuid"))
^
HINT: There is an entry for table "Lockers", but it cannot be
referenced from this part of the query.

===== Jenda(at)Krynicky(dot)cz === http://Jenda.Krynicky.cz =====
When it comes to wine, women and song, wizards are allowed
to get drunk and croon as much as they like.
-- Terry Pratchett in Sourcery