Message-Id: <m11nVrB-0003kLC@orion.SAPserv.Hamburg.dsh.de>
From: wieck@debis.com (Jan Wieck)
Subject: Re: [SQL] NULL
To: pgman@candle.pha.pa.us (Bruce Momjian)
Date: Tue, 16 Nov 1999 00:48:21 +0100 (MET)
Cc: goran@kirra.net, pgsql-sql@postgreSQL.org
Reply-To: wieck@debis.com (Jan Wieck)
In-Reply-To: <199911151924.OAA21880@candle.pha.pa.us> from "Bruce Momjian" at
	Nov 15, 99 02:23:58 pm
Content-Type: text

Bruce Momjian wrote:

> [Charset iso-8859-1 unsupported, filtering to ASCII...]
> >
> > How about this according to SQL standard:
> >
> > CREATE TABLE x { y integer NULL };
> >
> > It suppose to mean that NULLs are explicitly allowed in
> > this field.
> > Is this required by SQL-92?
>
> If I remember correctly, only NOT NULL is supported by SQL-92.  Thomas
> talked about adding support for it in some limited cases for 7.0.  There
> are shift/reduce cases if it were allowed everywhere.

Hmmm,

    I can't see any shift/reduce conflicts if I place a

        | NULL_P

    case into the ColConstraintElem: definition right between the

        | DEFAULT b_expr

    and

        | NOT NULL_P

    cases. Could it be that this reason is out of date?


Jan

--

#======================================================================#
# It's easier to get forgiveness for being wrong than for being right. #
# Let's break this rule - forgive me.                                  #
#========================================= wieck@debis.com (Jan Wieck) #