"Christopher Kings-Lynne" <chriskl@familyhealth.com.au> writes:
>> Come to think of it, that's probably a bug: you should not be able to
>> DROP NOT NULL on a column that's part of a PRIMARY KEY. Unless you
>> cascade to remove the primary key, that is.
> I did ask you about this before, Tom :)
> The DROP NOT NULL code I submitted will not allow you to drop a not null on
> a column that participates in a primary key. I was very careful about that.
Duh, so you were.
> So basically, it's a restrict-only implementation. Although it would be
> fairly easy I guess to make it support cascade and restrict keywords...?
> Perhaps not thru the dependency mechanism, but it can be done explicitly.
Yeah, I doubt it's worth trying to force NOT NULL into the dependency
mechanism for this. Do you feel like trying to do it "by hand"? It
doesn't seem like a very important issue to me.
regards, tom lane
