Re: INSERT ... ON CONFLICT doesn't work
От | Tom Lane |
---|---|
Тема | Re: INSERT ... ON CONFLICT doesn't work |
Дата | |
Msg-id | 1990141.1638388378@sss.pgh.pa.us обсуждение исходный текст |
Ответ на | Re: INSERT ... ON CONFLICT doesn't work ("David G. Johnston" <david.g.johnston@gmail.com>) |
Ответы |
Re: INSERT ... ON CONFLICT doesn't work
Re: INSERT ... ON CONFLICT doesn't work |
Список | pgsql-general |
"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
В списке pgsql-general по дате отправления: