| From: | Gregory Stark <stark(at)enterprisedb(dot)com> |
|---|---|
| To: | "Heikki Linnakangas" <heikki(at)enterprisedb(dot)com> |
| Cc: | "Pavel Stehule" <pavel(dot)stehule(at)gmail(dot)com>, <pgsql-bugs(at)postgresql(dot)org> |
| Subject: | Re: ON DELETE SET NULL clauses do error when more than two columns are referenced to one table |
| Date: | 2007-08-13 13:10:40 |
| Message-ID: | 87y7gfshpr.fsf@oxford.xeocode.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs pgsql-patches |
"Heikki Linnakangas" <heikki(at)enterprisedb(dot)com> writes:
> I'm not sure what to do about this. We could change the order the
> triggers are fired to breadth-first. If all the setnull triggers were
> executed first, there would be no problem. But that seems like a pretty
> big change, and I'm afraid it might have other unintended consequences.
We could also check the queued triggers to see if there really is a trigger
which will be invalidated by the second update and therefore needs to be
rechecked (or even just change the tid of the existing queued check). I don't
know what it would take to make that efficient though.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Brian Hirt | 2007-08-13 13:43:26 | Re: failed to re-find parent key in "..." for deletion target page |
| Previous Message | Heikki Linnakangas | 2007-08-13 12:32:42 | Re: ON DELETE SET NULL clauses do error when more than two columns are referenced to one table |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2007-08-13 14:44:22 | Re: ON DELETE SET NULL clauses do error when more than two columns are referenced to one table |
| Previous Message | Heikki Linnakangas | 2007-08-13 12:32:42 | Re: ON DELETE SET NULL clauses do error when more than two columns are referenced to one table |