Skip site navigation (1) Skip section navigation (2)

Re: Allow setObject(x,y,Types.BIT) if y is a Number &

From: Kim Ho <kho(at)redhat(dot)com>
To: PostgreSQL-patches <pgsql-patches(at)postgresql(dot)org>
Cc: pgsql-jdbc-list <pgsql-jdbc(at)postgresql(dot)org>,Darin Ohashi <DOhashi(at)maplesoft(dot)com>,Fernando Nasser <fnasser(at)redhat(dot)com>
Subject: Re: Allow setObject(x,y,Types.BIT) if y is a Number &
Date: 2003-06-27 22:28:27
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-jdbcpgsql-patches
On Wed, 2003-06-18 at 13:09, Kim Ho wrote:
> Problem:
>  - setObject(x,y,Types.BIT) throws an exception if y is a Number
>  - getObject() on a bit column will return null instead of True or False
> Boolean objects
Added Problem:
 - Doesn't set bit columns

> Fix:
>  - Added check in setObject() to check to that the Number has value==1.
> If so, set to True. False otherwise. This seems to be consistent with
> the rest of the code.
>  - Added BIT to JDBC datatype list
 - Using way to set values in both boolean/bit type columns

It works now.

The following program works now:

Statement stmt = con.createStatement();
stmt.execute("Create Table bit_tab (b bit)");
PreparedStatement pstmt = con.prepareStatement("insert into bit_tab
values (?)");

Sorry bout the delay.



In response to


pgsql-patches by date

Next:From: Joe ConwayDate: 2003-06-27 23:26:56
Subject: Re: connectby_reverselookup()
Previous:From: Joe ConwayDate: 2003-06-27 22:14:27
Subject: Re: array support patch phase 1 patch

pgsql-jdbc by date

Next:From: Tom LaneDate: 2003-06-28 02:50:13
Subject: Re: Client_encoding
Previous:From: Kim HoDate: 2003-06-27 21:49:19
Subject: Re: BIT vs boolean

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group