Re: Throwing NumberFormat exception for preparedStatement.setObjcet() - Mailing list pgsql-jdbc

From Kris Jurka
Subject Re: Throwing NumberFormat exception for preparedStatement.setObjcet()
Date
Msg-id alpine.BSO.2.00.1001131733040.3231@leary.csoft.net
Whole thread Raw
In response to Re: Throwing NumberFormat exception for preparedStatement.setObjcet()  (Dave Cramer <pg@fastcrypt.com>)
Responses Re: Throwing NumberFormat exception for preparedStatement.setObjcet()
List pgsql-jdbc

On Tue, 12 Jan 2010, Dave Cramer wrote:

> If I were writing it I would use java.sql.Types.Integer as the
> columnType, not the numeric value. And inputData should be an Integer.
>

inputData can perfectly well be a String.  That's the whole point of the
three argument version of this method, to provide such a conversion for
the user.

The reason it's throwing a NumberFormatException is that you're passing
something which isn't a number.  With a later driver version you wouldn't
get this exception, but instead the server would complain that it wasn't a
valid number.

The attached test case shows this working just fine from my perspective.

Kris Jurka

Attachment

pgsql-jdbc by date:

Previous
From: Dave Cramer
Date:
Subject: Re: Throwing NumberFormat exception for preparedStatement.setObjcet()
Next
From: Racker Vijay
Date:
Subject: Re: Best Practice to Create a Connection Pool in PostgreSQL