From: | Michael Glaesemann <grzm(at)myrealbox(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Stephan Szabo <sszabo(at)megazone(dot)bigpanda(dot)com>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Foreign keys for non-default datatypes |
Date: | 2006-03-04 01:01:46 |
Message-ID: | 5D9008CC-D706-4656-98FD-B5C052ECECB0@myrealbox.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Mar 4, 2006, at 9:22 , Tom Lane wrote:
> If we did this then RI checks would no longer be subvertible by
> rules or
> user triggers. Although I've been heard to argue that that's a
> feature,
> I think the majority of people feel it's a bug, and wouldn't be
> sorry to
> see it go.
Just to check, are you referring to constraint triggers here? (I
don't believe so, as I've been using constraint triggers in cases
other than referential integrity and as I read it, you're only
referring to RI.) Currently constraint triggers are the only way to
defer constraint checking to the end of a transaction. Until we have
some kind of support for multiple updates in a single statement (or
perhaps deferred constraints, but I'd prefer the former), I'd like
constraint triggers to hang around.
Michael Glaesemann
grzm myrealbox com
From | Date | Subject | |
---|---|---|---|
Next Message | Matthew T. O'Connor | 2006-03-04 01:46:25 | Re: Automatic free space map filling |
Previous Message | Tom Lane | 2006-03-04 00:58:10 | Re: Automatic free space map filling |