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 AAA83645 for ; Sun, 12 Dec 1999 00:53:52 -0500 (EST) (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 AAA25417; Sun, 12 Dec 1999 00:53:20 -0500 (EST) To: Brent Wood cc: pgsql-sql@postgreSQL.org Subject: Re: [SQL] polygon problem In-reply-to: Your message of Sun, 12 Dec 1999 10:32:44 +1300 <3852C2FC.BF4B14A7@blazemail.com> Date: Sun, 12 Dec 1999 00:53:19 -0500 Message-ID: <25415.944977999@sss.pgh.pa.us> From: Tom Lane Brent Wood writes: > insert into table1 values ('poly1',((0,0),(0,1),(1,0)),'s'); > This fails with the msg: > ERROR: parser: parser error at or near "," I think you need quotes around the polygon value, ie, insert into table1 values ('poly1','((0,0),(0,1),(1,0))','s'); As a rule of thumb, the only datatypes that don't need quotes around literal values in SQL statements are numeric types. Our SQL parser doesn't understand weird datatypes like polygon --- it wants a string literal, which it'll eventually hand off to the type-specific input routine for the datatype. regards, tom lane