Re: Throwing NumberFormat exception for preparedStatement.setObjcet()

Поиск
Список
Период
Сортировка
Искать
От
Kris Jurka
Тема
Re: Throwing NumberFormat exception for preparedStatement.setObjcet()
Дата
Msg-id
alpine.BSO.2.00.1001131733040.3231@leary.csoft.net
Ответ на
Список
Дерево обсуждения
Throwing NumberFormat exception for preparedStatement.setObjcet() Srinivas Gunnam <srinivas_gunnam@persistent.co.in>
Re: Throwing NumberFormat exception for preparedStatement.setObjcet() Dave Cramer <pg@fastcrypt.com>
Re: Throwing NumberFormat exception for preparedStatement.setObjcet() Srinivas Gunnam <srinivas_gunnam@persistent.co.in>
Re: Throwing NumberFormat exception for preparedStatement.setObjcet() Dave Cramer <pg@fastcrypt.com>
Re: Throwing NumberFormat exception for preparedStatement.setObjcet() Kris Jurka <books@ejurka.com>
Re: Throwing NumberFormat exception for preparedStatement.setObjcet() Srinivas Gunnam <srinivas_gunnam@persistent.co.in>
Re: Throwing NumberFormat exception for preparedStatement.setObjcet() dmp <danap@ttc-cmc.net>


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
В списке pgsql-jdbc по дате отправления
От: Dave Cramer
Дата:
От: Racker Vijay
Дата:
FAQ