On Fri, Apr 01, 2005 at 10:37:11 +0200,
[EMAIL PROTECTED] wrote:
>
> And idea that just came up around here that sounds like a pretty neat
> workaround, which we're gonna try, is to drop the foreign key
> constraints, and just use a check constraint for the allowed values. If
> the cardinality of the reference table is small, this is much faster
> than using foreign keys and solves your problem. With the drawback that
> if you update the reference table (if you keep it), you mustn't forget
> to also update the check constraints in more than one place.
Using domains is a good way to keep column constraints in just one place.
---------------------------(end of broadcast)---------------------------
TIP 5: Have you checked our extensive FAQ?
http://www.postgresql.org/docs/faq
