On Sep 7, 2009, at 6:10 PM, Tom Lane wrote:
Alvaro Herrera alvhe...@commandprompt.com writes:
Pavel Stehule escribió:
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
Mark Reid wrote:
It'll similarly break any code where a result of UPDATE 0 is assumed to
indicate that the record does not exist.
I wonder if this could be helped if the trigger had a way of overriding
the emitted command tag.
There are countless reports of trouble because somebody has an
2009/9/7 Alvaro Herrera alvhe...@commandprompt.com:
Mark Reid wrote:
It'll similarly break any code where a result of UPDATE 0 is assumed to
indicate that the record does not exist.
I wonder if this could be helped if the trigger had a way of overriding
the emitted command tag.
There are
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
Tom Lane escribió:
Alvaro Herrera alvhe...@commandprompt.com writes:
Pavel Stehule escribi�:
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.
Alvaro Herrera alvhe...@commandprompt.com writes:
Pavel Stehule escribió:
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.
And how is the user going to
2009/9/8 Alvaro Herrera alvhe...@commandprompt.com:
Tom Lane escribió:
Alvaro Herrera alvhe...@commandprompt.com writes:
Pavel Stehule escribió:
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
