From: | Stephan Szabo <sszabo(at)megazone23(dot)bigpanda(dot)com> |
---|---|
To: | Estelle_Littee(at)etu(dot)u-bourgogne(dot)fr |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: inheritance and foreign key |
Date: | 2001-03-09 19:57:33 |
Message-ID: | Pine.BSF.4.21.0103091155470.81537-100000@megazone23.bigpanda.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Yes, it's currently not implemented (see other currently
running thread in pgsql-general about this topic)
On Fri, 9 Mar 2001 Estelle_Littee(at)etu(dot)u-bourgogne(dot)fr wrote:
> Hello,
>
> We have the following schema :
> create table A (id_A integer primary key,b_A integer);
> create table B (a_B integer) inherits A;
> create table C (id_C integer primary key, b_C integer);
> create table D (id1 integer references A (id_A),
> id2 integer references C (id_C),
> primary key(id1, id2));
>
> Problem occurs when we want to insert a tuple into D
> that references a B's tuple. Our idea is :
> create table D (id1 integer references A* (id_A),
> id2 integer references C (id_C),
> primary key(id1, id2));
> which is not allowed by postgres.
>
> Does anyone has experimented such problem?
From | Date | Subject | |
---|---|---|---|
Next Message | Stephan Szabo | 2001-03-09 20:03:07 | Re: functions for triggers: passing parameters |
Previous Message | Patrick Welche | 2001-03-09 19:43:28 | Re: [SQL] Re: MySQLs Describe emulator! |