Received: from localhost (IDENT:root@hectic-1.jpl.nasa.gov [128.149.68.203]) by hub.org (8.9.3/8.9.3) with ESMTP id LAA91001 for ; Fri, 30 Jul 1999 11:29:53 -0400 (EDT) (envelope-from lockhart@alumni.caltech.edu) Received: from alumni.caltech.edu (lockhart@localhost [127.0.0.1]) by localhost (8.8.7/8.8.7) with ESMTP id PAA10901; Fri, 30 Jul 1999 15:29:37 GMT Sender: lockhart@hub.org Message-ID: <37A1C4E1.F56DED39@alumni.caltech.edu> Date: Fri, 30 Jul 1999 15:29:37 +0000 From: Thomas Lockhart X-Mailer: Mozilla 4.6 [en] (X11; I; Linux 2.0.36 i686) X-Accept-Language: en MIME-Version: 1.0 To: "Mengelbier, Magnus" CC: "'pgsql-interfaces@postgresql.org'" Subject: Re: [INTERFACES] parser: parse error at or near... with create table References: <81F0C610BC68D2118F110008C7242DE51EAB58@luex1.clinicaldatacare.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit > We wonder if any one has experience from an error (which is probably a > newbie misstake on our part) that pops up when we are trying to create a > simple table with pgAccess in a postgreSQL database. We have recieved the > same type of error on more complex table builds. The message is ... > Error executing query > create table "asdfs" ("fds" serial NOT NULL ) > PostgreSQL error message: > Error: parser: parse error at or near "not" > PostgreSQL status: PGRES_FATAL_ERROR 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 ;) - Thomas -- Thomas Lockhart lockhart@alumni.caltech.edu South Pasadena, California