From: | Rod Taylor <rbt(at)zort(dot)ca> |
---|---|
To: | Neil Conway <neilc(at)samurai(dot)com> |
Cc: | PostgreSQL Patches <pgsql-patches(at)postgresql(dot)org> |
Subject: | Re: CREATE TABLE docs fix |
Date: | 2002-09-01 17:44:37 |
Message-ID: | 1030902278.8617.95.camel@jester |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-patches |
On Sun, 2002-09-01 at 13:28, Neil Conway wrote:
> Rod Taylor <rbt(at)zort(dot)ca> writes:
>
> > On Sun, 2002-09-01 at 04:00, Neil Conway wrote:
> > > This patch fixes a minor inaccuracy in the documentation: NOT NULL
> > > is not synonymous with CHECK (xxx IS NOT NULL) -- for example,
> > > consider ALTER TABLE ADD PRIMARY KEY, which checks for 'NOT NULL',
> > > not a check constraint.
> >
> > Yeah, but they're still synonymous.
>
> How so? Their behavior is clearly different (note the case above, as
> well as any other situation in which the system attempts to determine
> if a column allows a NULL value).
>
> Since they are not interchangeable, they can't be synonyms.
The case you brought up is more of a bug or mis-implementation of alter
table / add primary key. I guess you're right. They're not, but they
should be.
From | Date | Subject | |
---|---|---|---|
Next Message | Alvaro Herrera | 2002-09-01 18:07:30 | Re: CREATE TABLE docs fix |
Previous Message | Neil Conway | 2002-09-01 17:28:35 | Re: CREATE TABLE docs fix |