On 16 Jun 2011, at 7:04, Mike Christensen wrote: > I know I can setup a FK constraint to make sure Table1.ColA exists in > Table2.Key, however what if I want to do the reverse? > > I want to ensure Table1.ColA does NOT exist in Table2.Key.. Can I do > this with any sort of CHECK constraint, trigger, custom function, etc? > Thanks! Perhaps it's possible to use a unique constraint in a third table to guarantee those foreign keys can never have the same value. That would probably be more efficient than executing stored procedure code. Alban Hertroys -- Screwing up is an excellent way to attach something to the ceiling. !DSPAM:737,4dfa49a012091645294739! -- Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general