From: | Stephan Szabo <sszabo(at)megazone23(dot)bigpanda(dot)com> |
---|---|
To: | Franz J Fortuny <ffortuny(at)ivsol(dot)com> |
Cc: | pgsql-sql(at)postgresql(dot)org |
Subject: | Re: Referential integrity: broken rule? |
Date: | 2000-10-11 22:15:09 |
Message-ID: | Pine.BSF.4.10.10010111509500.35777-100000@megazone23.bigpanda.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-sql |
Yes, I believe it is mentioned in the docs (well at least the
sgml source, I don't have a compiled doc set) as a bug
of the implementation somewhere in the section on references.
7.1 should fail for this case, although it doesn't properly deal with
dropping the unique constraint later.
Stephan Szabo
sszabo(at)bigpanda(dot)com
On Wed, 11 Oct 2000, Franz J Fortuny wrote:
> This table:
>
> create table things
> (
> idthing integer not null,
> isthis boolean not null
> primary key(idthing,isthis)
> ....
>
> )
>
> would be referenced by this one:
>
> create table forthings
> (
> fromthing integer not null references things(idthing),
>
> ....
>
> )
>
> The above SHOULD NOT be accepted, since table "things" did not declare
> idthing as UNIQUE. However, it IS accepted under PostgreSQL (7.0.2).
From | Date | Subject | |
---|---|---|---|
Next Message | karasiov | 2000-10-12 08:51:49 | set digest |
Previous Message | Franz J Fortuny | 2000-10-11 19:18:26 | Referential integrity: broken rule? |