Re: Re: [COMMITTERS] pgsql: Add support for INSERT ... ON CONFLICT DO NOTHING/UPDATE.
| От | Tom Lane |
|---|---|
| Тема | Re: Re: [COMMITTERS] pgsql: Add support for INSERT ... ON CONFLICT DO NOTHING/UPDATE. |
| Дата | |
| Msg-id | 10660.1432171328@sss.pgh.pa.us обсуждение исходный текст |
| Ответ на | Re: Re: [COMMITTERS] pgsql: Add support for INSERT ... ON CONFLICT DO NOTHING/UPDATE. (Andres Freund <andres@anarazel.de>) |
| Ответы |
Re: Re: [COMMITTERS] pgsql: Add support for INSERT ... ON
CONFLICT DO NOTHING/UPDATE.
Re: Re: [COMMITTERS] pgsql: Add support for INSERT ... ON CONFLICT DO NOTHING/UPDATE. Re: Re: [COMMITTERS] pgsql: Add support for INSERT ... ON CONFLICT DO NOTHING/UPDATE. |
| Список | pgsql-hackers |
Andres Freund <andres@anarazel.de> writes:
> You realize there's other instances of this in the same damn function?
Not to mention that several places in libpq/fe-exec.c should be
taught about this new tag. And who-knows-what in other client-side
libraries. I am not really sure that it was a good idea to invent
this command tag. In fact, I'm pretty sure it was a *bad* idea ---
what will happen if we ever create a statement actually named UPSERT?
I think we should fix this by ripping out the variant tag, not trying
to propagate it everywhere it would need to go. Cute ideas are not
the same as good ideas.
regards, tom lane
В списке pgsql-hackers по дате отправления: