| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
| Cc: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, Mark Reid <mark(at)markreid(dot)org>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: manually setting the command tag (was Re: 8.4: suppress_redundant_updates trigger vs. "Upsert" logic) |
| Date: | 2009-09-07 23:10:05 |
| Message-ID: | 11808.1252365005@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs pgsql-hackers |
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?
I don't think that "put it on the user's shoulders" is a good solution.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2009-09-07 23:25:20 | Re: manually setting the command tag (was Re: 8.4: suppress_redundant_updates trigger vs. "Upsert" logic) |
| Previous Message | Alvaro Herrera | 2009-09-07 22:45:27 | Re: manually setting the command tag (was Re: 8.4: suppress_redundant_updates trigger vs. "Upsert" logic) |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David E. Wheeler | 2009-09-07 23:13:35 | Snow Leopard Features |
| Previous Message | Robert Haas | 2009-09-07 23:06:46 | Re: LATERAL |