From: | Stephan Szabo <sszabo(at)megazone(dot)bigpanda(dot)com> |
---|---|
To: | Mike Mascari <mascarm(at)mascari(dot)com> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Any plans on allowing user-defined triggers to be |
Date: | 2004-10-26 14:55:17 |
Message-ID: | 20041026075423.G93326@megazone.bigpanda.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Tue, 26 Oct 2004, Mike Mascari wrote:
> Stephan Szabo wrote:
> > On Tue, 26 Oct 2004, Mike Mascari wrote:
> >
> >
> >>I'd like to ensure that the creation of a department also implies the
> >>creation of two to eight projects; no more, no less:
>
> >>Is there no way to achieve the above stated goal in the server? Must I
> >>rely on the application to enforce consistency?
> >
> >
> > Well. It's not exactly meant to be a user facing feature, but check out
> > CREATE CONSTRAINT TRIGGER.
>
> Thanks, Stephan!
>
> I read the disclaimer "It is not intended for general use" but am
> curious as to why it isn't a user-facing feature? Is it a function of
> just exposing a cleaner SQL interface, or is it a function of the
> trigger queue having been written after user-defined triggers, or is
> there some philosophical argument against allowing user-definable
> triggers to be deferred?
I should also add that it's also not likely to get upgraded to handle new
trigger features (for example statement triggers) quickly unless someone
wants to step up and do so.
From | Date | Subject | |
---|---|---|---|
Next Message | Henk Ernst Blok | 2004-10-26 14:58:46 | Re: Strange count(*) implementation? |
Previous Message | Stephan Szabo | 2004-10-26 14:51:34 | Re: Any plans on allowing user-defined triggers to be |