From: | Tatsuo Ishii <t-ishii(at)sra(dot)co(dot)jp> |
---|---|
To: | dhogaza(at)pacifier(dot)com |
Cc: | scrappy(at)hub(dot)org, tgl(at)sss(dot)pgh(dot)pa(dot)us, webmaster(at)postgreSQL(dot)org, pgsql-hackers(at)postgreSQL(dot)org |
Subject: | Re: [HACKERS] Beta for 4:30AST ... ? |
Date: | 2000-02-22 04:45:39 |
Message-ID: | 20000222134539N.t-ishii@sra.co.jp |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> At 07:57 PM 2/21/00 -0400, The Hermit Hacker wrote:
>
> > * -Add referential integrity(Jan)[primary]
>
> This is only PARTIALLY complete:
>
> MATCH FULL and MATCH <unspecified> foreign keys and their related
> referential actions are complete. MATCH PARTIAL isn't in - I'll be
> doing that for 7.1.
>
> It doesn't check that the columns referenced in a foreign key
> form a primary key or are contrained by UNIQUE in the referenced
> table. This will be checked in 7.1, not sure who will do it (who
> ever gets to it first, probably).
>
> Those are the two major user-visible loose ends with this feature.
What about ALTER TABLE table DROP CONSTRAINT? I see this:
alter table t1 drop constraint t1_fk cascade;
ERROR: ALTER TABLE / DROP CONSTRAINT is not implemented
Note that we seem to have ALTER TABLE table ADD CONSTRAINT, though.
--
Tatsuo Ishii
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2000-02-22 04:53:09 | Re: [HACKERS] Numeric with '-' |
Previous Message | Tom Lane | 2000-02-22 04:19:28 | Re: [HACKERS] Re: SQL compliance - why -- comments only at psql level? |