Chris Curvey <[email protected]> wrote: > Perhaps a pair of triggers? An insert-or-update trigger on foo, and a > delete-or-update trigger on bar?
Using a foreign key constraint is best if that can do the right thing. If that doesn't work, triggers like you describe are probably the best option, but you need to cover race conditions. See this recent post for suggestions: http://www.postgresql.org/message-id/[email protected] -- Kevin Grittner EDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-general mailing list ([email protected]) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
