Return-Path: Mailing-List: contact torque-dev-help@db.apache.org; run by ezmlm Delivered-To: mailing list torque-dev@db.apache.org Received: (qmail 42629 invoked from network); 29 Apr 2003 02:35:29 -0000 Received: from mx1.wisernet.com (216.7.11.232) by daedalus.apache.org with SMTP; 29 Apr 2003 02:35:29 -0000 Received: from bitcount.com [207.127.234.138] by mx1.wisernet.com with Novonyx SMTP Server $Revision: 2.25.1.0 $; Mon, 28 Apr 2003 22:35:35 -0400 (EDT) Message-ID: <3EADE4EB.9030003@bitcount.com> Date: Mon, 28 Apr 2003 22:35:23 -0400 From: Matt Finn User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.3) Gecko/20030312 X-Accept-Language: en-us, en MIME-Version: 1.0 To: torque-dev@db.apache.org Subject: Re: Postgres aapter bug Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Hi, I have also been afflicted with that problem. How about using single quotes for booleans ('0' and '1')? This works fine with 7.2 and 7.3 postgres across all three types, although I haven't tested any earlier versions. postgres=# create table test (one boolean, two char, three int2); CREATE TABLE postgres=# insert into test (one,two,three) values ('0','0','0'); INSERT 43810 1 postgres=# insert into test (one,two,three) values ('1','1','1'); INSERT 43811 1 postgres=# select * from test; one | two | three -----+-----+------- 0 | f | 0 1 | t | 1 (2 rows) postgres=# -matt