Re: Wrong SqlType for boolean columns

From: Kris Jurka <books(at)ejurka(dot)com>
To: Thomas Kellerer <spam_eater(at)gmx(dot)net>
Cc: pgsql-jdbc(at)postgresql(dot)org
Subject: Re: Wrong SqlType for boolean columns
Date: 2010-07-28 16:57:58
Message-ID: alpine.BSO.2.00.1007281255450.9018@leary.csoft.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-jdbc

On Wed, 28 Jul 2010, Thomas Kellerer wrote:

> Oliver Jowett, 28.07.2010 10:59:
>> It is not a bug. BOOLEAN does not exist in earlier JDBC versions,
>> and drivers can map boolean types to either BIT or BOOLEAN. We pick
>> BIT so we can build drivers for earlier JDBC versions. (BIT is
>> something of a confusing type, as the mappings defined by JDBC for
>> the JDBC BIT type only really make sense for a single boolean value,
>> not a SQL BIT(n) type)
>
> Wouldn't it make sense to map this to BOOLEAN if the driver is built for
> JDBC4 and to BIT if is built for JDBC3?
>

Actually BIT is JDBC2 and BOOLEAN is JDBC3. Since we no longer build
JDBC2 releases for the latest drivers, we could make this change, I'm just
not sure I see the point. I guess we'd get fewer of these complaints.

Kris Jurka

In response to

Browse pgsql-jdbc by date

  From Date Subject
Next Message James William Pye 2010-07-28 20:19:26 Re: [HACKERS] Trouble with COPY IN
Previous Message Kris Jurka 2010-07-28 16:53:49 Re: [HACKERS] Trouble with COPY IN