From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | "Christopher Kings-Lynne" <chriskl(at)familyhealth(dot)com(dot)au> |
Cc: | "Hackers" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: New manual chapters |
Date: | 2002-08-06 03:54:19 |
Message-ID: | 5532.1028606059@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
"Christopher Kings-Lynne" <chriskl(at)familyhealth(dot)com(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Hannu Krosing | 2002-08-06 04:23:28 | Re: New manual chapters |
Previous Message | Hannu Krosing | 2002-08-06 03:36:23 | Re: New manual chapters |