From: | Stephan Szabo <sszabo(at)megazone23(dot)bigpanda(dot)com> |
---|---|
To: | Josh Berkus <josh(at)agliodbs(dot)com> |
Cc: | <pgsql-sql(at)postgresql(dot)org> |
Subject: | Re: Constraint problem |
Date: | 2002-05-17 18:42:43 |
Message-ID: | 20020517114156.Q20428-100000@megazone23.bigpanda.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-sql |
On Thu, 16 May 2002, Josh Berkus wrote:
> Stephan,
>
> > AFAIK we don't actually have statement triggers right now, anyway,
> > but...
> > Actually, I guess an after trigger that just checked the new values
> > would
> > work as well, right? See if there exists more than one row with the
> > new
> > key value. The after trigger should fire after all the changes are
> > done
> > and in the worst case you could use constraint triggers and
> > deferment.
> > The hard part about this really is making it work with concurrent
> > modifications, and if you're willing to forgo that, it shouldn't be
> > too
> > bad.
>
> Thanks. I'll give your solution a try and see what the performance hit
> is.
>
> Is the Unique Constraint issue on the To-Do list?
I'm not sure. I know it's been mentioned in the past, so probably (too
lazy to look right now).
From | Date | Subject | |
---|---|---|---|
Next Message | Christian Rishoej | 2002-05-17 23:39:04 | Rules and variables? |
Previous Message | Jan Wieck | 2002-05-17 18:19:31 | Re: Rules and Triggers |