| From: | "Norman J(dot) Clarke" <norman(at)combimatrix(dot)com> |
|---|---|
| To: | "Dominic J(dot) Eidson" <sauron(at)the-infinite(dot)org> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: avoiding endless loop in an UPDATE trigger |
| Date: | 2001-02-26 22:31:05 |
| Message-ID: | Pine.LNX.4.21.0102261427430.29026-100000@curly.combimatrix.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Right. I already figured this out, which is why in my email I said "the
problem with this is..."
If you have any suggestions on how to avoid getting into this kind of loop
without disabling triggers (so that my foreign keys still work) I'd very
much appreciate your suggestions.
Thanks!
Norman
On Mon, 26 Feb 2001, Dominic J. Eidson wrote:
> On Mon, 26 Feb 2001, Norman J. Clarke wrote:
>
> > The problem with this is that it disables all of my FOREIGN KEY
> > constraints during function execution, which is undesirable.
>
> Foreign Key constraints are implemented as triggers, IIRC. I'll let you
> figure out the implication(s) yourself.
>
>
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Richardson | 2001-02-26 22:57:04 | Re: Trigger and Permissions |
| Previous Message | Aristide Aragon | 2001-02-26 21:53:56 | Re: Help with pq++ |