Re: [PATCH] Return command tag 'REPLACE X' for CREATE OR REPLACE statements.
От | Alvaro Herrera |
---|---|
Тема | Re: [PATCH] Return command tag 'REPLACE X' for CREATE OR REPLACE statements. |
Дата | |
Msg-id | 1295014817-sup-5347@alvh.no-ip.org обсуждение исходный текст |
Ответ на | Re: [PATCH] Return command tag 'REPLACE X' for CREATE OR REPLACE statements. (Robert Haas <robertmhaas@gmail.com>) |
Ответы |
Re: [PATCH] Return command tag 'REPLACE X' for CREATE OR
REPLACE statements.
Re: [PATCH] Return command tag 'REPLACE X' for CREATE OR REPLACE statements. |
Список | pgsql-hackers |
Excerpts from Robert Haas's message of vie ene 14 08:40:07 -0300 2011: > Also, I don't really like the way this spreads knowledge of the > completionTag out all over the backend. I think it would be better to > follow the existing model used by the COPY and COMMIT commands, > whereby the return value indicates what happened and > standard_ProcessUtility() uses that to set the command tag. Yeah, that looks ugly. However it's already ugly elsewhere: for example see PerformPortalFetch. I am not sure if it should be this patch's responsability to clean that stuff up. (Maybe we should decree that at least this patch shouldn't make the situation worse.) -- Álvaro Herrera <alvherre@commandprompt.com> The PostgreSQL Company - Command Prompt, Inc. PostgreSQL Replication, Consulting, Custom Development, 24x7 support
В списке pgsql-hackers по дате отправления: