Pavel Stehule escribió: > 2009/9/7 Alvaro Herrera <alvhe...@commandprompt.com>:
> > There are countless reports of trouble because somebody has an INSTEAD > > rule in the table, and the tag emits something that's not quite > > acceptable for some outer software layer. The problem is that there's > > no way at all to make the command tag behave! > > > > For example, we could offer a new SPI function, say SPI_settag(), which > > sets the command tag string. PL/pgSQL could expose this via a new > > command, for example COMMANDTAG. > > Isn't better to solve the the correct diagnostics for INSTEAD rules or > triggers? As far as I can tell it's not possible to do better without letting the user put their hands on the tag. The problem is figuring out what command should determine the tag. -- Alvaro Herrera http://www.CommandPrompt.com/ The PostgreSQL Company - Command Prompt, Inc. -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
