>> 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.
I looked at drop constraint for the foreign key case while I was doing
add constraint, but right now the system doesn't generate unique
constraint names (although it should) so drop constraint could be
dangerous if you're not careful. Yeah, let me drop this RI constraint
'<unknown>' that I just created... oops... And unfortunately, to be
really compliant, all of the constraint names have to be unique, and
I really didn't want to hack something in that was going to make it
harder to do it right later.
Stephan
