BUG #1307: Possible bug inheritance/referential integrity - Mailing list pgsql-bugs

From PostgreSQL Bugs List
Subject BUG #1307: Possible bug inheritance/referential integrity
Date
Msg-id 20041106121149.76088739260@www.postgresql.com
Whole thread Raw
Responses Re: BUG #1307: Possible bug inheritance/referential integrity
Re: BUG #1307: Possible bug inheritance/referential integrity
List pgsql-bugs
The following bug has been logged online:

Bug reference:      1307
Logged by:          Thomas Jacob

Email address:      jacob@internet24.de

PostgreSQL version: 7.4.5

Operating system:   Gentoo Linux, Kernel 2.6.7

Description:        Possible bug inheritance/referential integrity

Details:

Rows inserted into a table "sub" inherited from a table
"super" do not seem to exist in the super-table from the point of
view of the foreign key constraint checker in references to the
"super"-table, even though a SELECT query displays the rows that
were inserted into sub also in super, as should be (See example
provided).

But they should exist, shouldn't they? Or do I simply not
understand PostgreSQL's inheritance model correctly?

CREATE TABLE super (id INT PRIMARY KEY);
CREATE TABLE super_ref (id INT REFERENCES super);
CREATE TABLE sub () INHERITS(super);

-- this works
INSERT INTO super VALUES(1); INSERT INTO super_ref VALUES(1);

-- clean up
DELETE FROM super_ref; DELETE FROM super;

-- this fails with: ERROR:  insert or update on table "super_ref" violates
foreign key constraint "$1"
INSERT INTO sub VALUES(1); INSERT INTO super_ref VALUES(1);

pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: domain on bit(N) type produces strange results
Next
From: Michael Fuhr
Date:
Subject: Re: BUG #1307: Possible bug inheritance/referential integrity