Re: INSERT ... ON CONFLICT doesn't work
| От | Jenda Krynicky |
|---|---|
| Тема | Re: INSERT ... ON CONFLICT doesn't work |
| Дата | |
| Msg-id | 61A7D54B.4950.34298622@Jenda.Krynicky.cz обсуждение исходный текст |
| Ответ на | Re: INSERT ... ON CONFLICT doesn't work (Tom Lane <tgl@sss.pgh.pa.us>) |
| Ответы |
Re: INSERT ... ON CONFLICT doesn't work
|
| Список | pgsql-general |
From: Tom Lane <tgl@sss.pgh.pa.us>
> "David G. Johnston" <david.g.johnston@gmail.com> writes:
> > On Wed, Dec 1, 2021 at 12:21 PM Jenda Krynicky <Jenda@krynicky.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@Krynicky.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
В списке pgsql-general по дате отправления: