Received: from candle.pha.pa.us (pgman@s5-03.ppp.op.net [209.152.195.67]) by hub.org (8.9.3/8.9.3) with ESMTP id OAA45507 for ; Mon, 15 Nov 1999 14:25:36 -0500 (EST) (envelope-from pgman@candle.pha.pa.us) Received: (from pgman@localhost) by candle.pha.pa.us (8.9.0/8.9.0) id OAA21880; Mon, 15 Nov 1999 14:24:17 -0500 (EST) From: Bruce Momjian Message-Id: <199911151924.OAA21880@candle.pha.pa.us> Subject: Re: [SQL] NULL In-Reply-To: <383059DA.9D2AF70D@kirra.net> from Goran Thyni at "Nov 15, 1999 08:07:06 pm" To: Goran Thyni Date: Mon, 15 Nov 1999 14:23:58 -0500 (EST) CC: pgsql-sql@postgreSQL.org X-Mailer: ELM [version 2.4ME+ PL65 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit [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. -- Bruce Momjian | http://www.op.net/~candle maillist@candle.pha.pa.us | (610) 853-3000 + If your life is a hard drive, | 830 Blythe Avenue + Christ can be your backup. | Drexel Hill, Pennsylvania 19026