From: | Kedar Rasik Parikh <kedarr(at)netcore(dot)co(dot)in> |
---|---|
To: | Luiz Eduardo Cantanhede Neri <lecneri(at)gmail(dot)com> |
Cc: | pgsql-novice(at)postgresql(dot)org |
Subject: | Re: INHERIT and FOREIGN KEY issues |
Date: | 2009-05-24 18:11:36 |
Message-ID: | 20090524234136.fxjtgf41ogswwo4o@port1.netcore.co.in |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-novice |
I believe you will have to say good bye to the foreign key constraint.
Its is not inherited, only the schema is, constraints and index will
have to be separately created per child table.
-Regards
Kedar Parikh
Quoting Luiz Eduardo Cantanhede Neri <lecneri(at)gmail(dot)com>:
> Hi,
> I'm trying to do something like this:
>
> BEGIN;
>
> CREATE TABLE A
> (
> idA serial not null primary key,
> someColumn text
> );
>
> CREATE TABLE B
> (
> someData text
> ) INHERITS(A);
>
> CREATE TABLE C
> (
> idC serial not null primary key,
> anotherColumn text
> );
>
> CREATE TABLE BC(
> idB int4,
> idC int4,
> FOREIGN KEY (idB) REFERENCES B(idA),
> FOREIGN KEY (idC) REFERENCES C(idC)
> );
>
> COMMIT;
>
> But When it is going to create the table BC, it gives an error:
>
> ERROR: there is no unique constraint matching given keys for referenced
> table "b"
>
> My question is: Shouldn't it get Table A primary key and create the foreign
> key?
>
> Thx
> Luiz Eduardo
>
From | Date | Subject | |
---|---|---|---|
Next Message | Daniel Staal | 2009-05-24 18:21:48 | Re: INHERIT and FOREIGN KEY issues |
Previous Message | Luiz Eduardo Cantanhede Neri | 2009-05-24 17:54:47 | INHERIT and FOREIGN KEY issues |