Re: manually setting the command tag (was Re: 8.4: suppress_redundant_updates trigger vs. "Upsert" logic)

Tom Lane escribió:
> Alvaro Herrera <alvherre(at)commandprompt(dot)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 do better? For example, what if there are
> two triggers trying to set the result, perhaps because two different
> commands have been generated by DO ALSO rules?

We would allow the user to set a policy. This provides the mechanism
for doing it. Right now there is no mechanism at all and we fail to do
anything.

> I don't think that "put it on the user's shoulders" is a good solution.

Is there a better idea?

--
Alvaro Herrera http://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.