From: wieck@debis.com
To: pgman@candle.pha.pa.us
Cc: goran@kirra.net
Cc: pgsql-sql@postgreSQL.org
Subject: Re: [SQL] NULL
Date: Tue, 16 Nov 1999 00:48:21 +0100 (MET)
Message-ID: <m11nVrB-0003kLC@orion.SAPserv.Hamburg.dsh.de> (raw)
In-Reply-To: <199911151924.OAA21880@candle.pha.pa.us>
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) #
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-sql@postgresql.org
Cc: wieck@debis.com, pgman@candle.pha.pa.us, goran@kirra.net
Subject: Re: [SQL] NULL
In-Reply-To: <m11nVrB-0003kLC@orion.SAPserv.Hamburg.dsh.de>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox