Received: from thor.tht.net (thor.tht.net [209.47.145.4]) by mail.postgresql.org (8.11.1/8.11.1) with ESMTP id eBDI78L07324 for ; Wed, 13 Dec 2000 13:07:08 -0500 (EST) (envelope-from tgl@sss.pgh.pa.us) Received: from sss.pgh.pa.us (sss.pgh.pa.us [209.114.132.154]) by thor.tht.net (8.9.3/8.9.3) with ESMTP id MAA81044 for ; Wed, 13 Dec 2000 12:59:20 GMT (envelope-from tgl@sss.pgh.pa.us) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.11.1/8.11.1) with ESMTP id eBDGwTQ09111; Wed, 13 Dec 2000 11:58:30 -0500 (EST) To: =?ISO-8859-2?Q?Borek_Lupom=ECsk=FD?= cc: Francis Solomon , pgsql-sql@postgresql.org Subject: Re: SQL parse error In-reply-to: References: Comments: In-reply-to =?ISO-8859-2?Q?Borek_Lupom=ECsk=FD?= message dated "Wed, 13 Dec 2000 14:59:32 +0100" Date: Wed, 13 Dec 2000 11:58:29 -0500 Message-ID: <9108.976726709@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200012/105 X-Sequence-Number: 438 =?ISO-8859-2?Q?Borek_Lupom=ECsk=FD?= writes: > When I do this, it works for me, too. But when I do it on my current > database, something breaks. Hm. The obvious question is: are you *sure* all the entries in your table look like "NNNN.N"? regards, tom lane