Lists: | pgsql-jdbc |
---|
From: | Vincent Stoessel <vincent(at)xaymaca(dot)com> |
---|---|
To: | pgsql-jdbc(at)postgresql(dot)org |
Subject: | Re: setBoolean() |
Date: | 2002-11-06 21:29:15 |
Message-ID: | 3DC989AB.40505@xaymaca.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Lists: | pgsql-jdbc |
for the record using setBoolean() on a pg boolean column
does not work, right? So is the standard practice just to make a char(1)
or BIT column to hold a Y/N T/F value?
Thanks
--
Vincent Stoessel
Linux Systems Developer
vincent xaymaca.com
From: | Dave Cramer <Dave(at)micro-automation(dot)net> |
---|---|
To: | Vincent Stoessel <vincent(at)xaymaca(dot)com> |
Cc: | "pgsql-jdbc(at)postgresql(dot)org" <pgsql-jdbc(at)postgresql(dot)org> |
Subject: | Re: setBoolean() |
Date: | 2002-11-07 00:23:28 |
Message-ID: | 1036628608.1391.33.camel@inspiron.cramers |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Lists: | pgsql-jdbc |
This is news to me, can you send me a test case?
Dave
On Wed, 2002-11-06 at 16:29, Vincent Stoessel wrote:
> for the record using setBoolean() on a pg boolean column
> does not work, right? So is the standard practice just to make a char(1)
> or BIT column to hold a Y/N T/F value?
> Thanks
--
Dave Cramer <Dave(at)micro-automation(dot)net>