From: Dennis <dennis@zserve.com>
To: pgsql-sql@postgresql.org
Subject: Forein Key Problem
Date: Thu, 7 Jun 2001 15:43:18 -0600
Message-ID: <9foshm$148o$2@news.tht.net> (raw)
Is This s bug:
create table A
(
key varchar(20) not null primary key
);
create table B
(
id serial not null primary key,
col1 varchar(20) not null,
col2 varchar(20) not null
);
alter table B create constraint fk_col1 foreign key ( col1 ) references A (
key ) on delete cascade on update cascade;
alter table B create constraint fk_col2 foreign key ( col2 ) references A (
key ) on delete cascade on update cascade;
SQL Creation and operation works fine. In the case that one row in table B
where col1 = col2, if I update A.key, I'll get a referential integrity
violation??
ie: ERROR: fk_col1 referential integrity violation - key referenced from B
not found in A.
Is there a way to make this type of constraint work with the update?
If not, is there a way to create a constraint so that col1 != col2 is
inforced?
Thanks in advance..
Dennis
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-sql@postgresql.org
Cc: dennis@zserve.com
Subject: Re: Forein Key Problem
In-Reply-To: <9foshm$148o$2@news.tht.net>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox