Received: from w3s.ie (www.w3s.ie [193.120.211.43]) by hub.org (8.9.3/8.9.3) with SMTP id NAA16161 for ; Fri, 30 Jul 1999 13:14:05 -0400 (EDT) (envelope-from brendan@w3s.ie) Received: from w3s.ie by w3s.ie (SMI-8.6/SMI-SVR4) id SAA10602; Fri, 30 Jul 1999 18:08:11 +0100 Message-Id: <199907301708.SAA10602@w3s.ie> X-Mailer: exmh version 2.0.2 To: pgsql-interfaces@postgresql.org Subject: Re: [INTERFACES] parser: parse error at or near... with create table In-Reply-To: Your message of "Fri, 30 Jul 1999 12:41:55 -0400." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 30 Jul 1999 18:13:47 +0000 From: "Brendan McKenna" Hi, My quick $0.02 worth... : : I guess the main question is, will we allow the serial type to be NULL. : If not will we allow the NOT NULL phrase anyway to simplify the grammar. : If yes to either then let's allow the phrase now. : I don't see how you can allow a serial value to be null, since that would defeat the purpose of a serial (presuming there were more than one NULL-valued serial in a table). I just don't see how, logically, a serial could allow NULLs (even if it may be desirable in some cases). On the other hand, I would allow the NOT NULL phrase, even though it's redundant. Brendan -- Brendan McKenna Technical Director Phone: +353-(0)61-338177 x4143 W3 Services Ltd. Fax: +353-(0)61-338065 Innovation Centre Email: brendan@w3s.ie National Technological Park Limerick Ireland