Re: New manual chapters

From: "Christopher Kings-Lynne" <chriskl(at)familyhealth(dot)com(dot)au>
To: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: "Hackers" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: New manual chapters
Date: 2002-08-06 03:06:04
Message-ID: GNELIHDDFBOCMGBFGEFOEEIGCDAA.chriskl@familyhealth.com.au
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> "Christopher Kings-Lynne" <chriskl(at)familyhealth(dot)com(dot)au> writes:
> > You say:
> > "All drop commands in PostgreSQL support specifying CASCADE. Of course"
> > Which isn't technically true for the ALTER TABLE/DROP NOT NULL
> statement..
>
> 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.
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.

Chris

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2002-08-06 03:08:55 Re: Proposal for psql wildcarding behavior w/schemas
Previous Message Tom Lane 2002-08-06 02:56:37 Re: New manual chapters