Message-Id: <m11AFjI-0000cIC@druid.net>
Subject: Re: [INTERFACES] parser: parse error at or near... with create table
In-Reply-To: <37A1C4E1.F56DED39@alumni.caltech.edu> from Thomas Lockhart at
	"Jul 30, 1999 03:29:37 pm"
To: lockhart@alumni.caltech.edu (Thomas Lockhart)
Date: Fri, 30 Jul 1999 12:41:55 -0400 (EDT)
From: "D'Arcy" "J.M." Cain <darcy@druid.net>
Cc: Magnus.Mengelbier@clinicaldatacare.com, pgsql-interfaces@postgreSQL.org
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

Thus spake Thomas Lockhart
> >         create table "asdfs" ("fds" serial   NOT NULL )
> By definition, the SERIAL type is NOT NULL, so I didn't bother
> allowing that clause in the parser. If you would like to see this
> feature documented, send patches on docs/src/sgml/datatype.sgml. Or
> maybe we should allow it, but it *is* redundant ;)

Given that serial is currently a hack and we plan to implement a real
serial type, we should consider what the real type will do.  Is it
still going to be special?  Will it act exactly as it does now?  Once
we determine that then we just make the parser accept what it will
need to accept then so that people can write their queries the way
they will have to then.

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.

-- 
D'Arcy J.M. Cain <darcy@{druid|vex}.net>   |  Democracy is three wolves
http://www.druid.net/darcy/                |  and a sheep voting on
+1 416 424 2871     (DoD#0082)    (eNTP)   |  what's for dinner.