Received: from sss.sss.pgh.pa.us (sss.pgh.pa.us [209.114.166.2])
	by hub.org (8.9.3/8.9.3) with ESMTP id LAA93744
	for <pgsql-interfaces@postgreSQL.org>;
	Fri, 30 Jul 1999 11:41:01 -0400 (EDT)
	(envelope-from tgl@sss.pgh.pa.us)
Received: from sss.sss.pgh.pa.us (localhost [127.0.0.1])
	by sss.sss.pgh.pa.us (8.9.1/8.9.1) with ESMTP id LAA11387;
	Fri, 30 Jul 1999 11:40:18 -0400 (EDT)
To: "Mengelbier, Magnus" <Magnus.Mengelbier@clinicaldatacare.com>
cc: "'pgsql-interfaces@postgresql.org'" <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 16:58:56 +0200
	<81F0C610BC68D2118F110008C7242DE51EAB58@luex1.clinicaldatacare.com>
Date: Fri, 30 Jul 1999 11:40:18 -0400
Message-ID: <11385.933349218@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>

"Mengelbier, Magnus" <Magnus.Mengelbier@clinicaldatacare.com> writes:
> 	Error executing query
> 	create table "asdfs" ("fds" serial   NOT NULL )
> 	PostgreSQL error message:
> 		Error: parser: parse error at or near "not"

Hmm.  NOT NULL is implied by SERIAL column type, so you can just omit
that clause, but it's irritating that the parser won't accept the
explicit specification.  It looks like the grammar is set up to allow
no column constraints except PRIMARY KEY after SERIAL.  That seems
unnecessarily restrictive...

			regards, tom lane