Possible bug in inheritance/referential integrity

Started by Thomas Jacobover 21 years ago1 messagesbugs
Jump to latest
#1Thomas Jacob
jacob@internet24.de

============================================================================
POSTGRESQL BUG REPORT TEMPLATE
============================================================================

Your name : Thomas Jacob
Your email address : jacob@internet24.de

System Configuration
---------------------
Architecture (example: Intel Pentium) : AMD Duron

Operating System (example: Linux 2.4.18) : Linux 2.6.7

PostgreSQL version (example: PostgreSQL-7.4.6): PostgreSQL-7.4.6

Compiler used (example: gcc 2.95.2) : gcc 3.3.4

Please enter a FULL description of your problem:
------------------------------------------------

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?

Please describe a way to repeat the problem. Please try to provide a
concise reproducible example, if at all possible:
----------------------------------------------------------------------

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);

If you know how this problem might be fixed, list the solution below:
---------------------------------------------------------------------