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

Re: PreparedStatement#setString on non-string parameters

From: Dave Cramer <pg(at)fastcrypt(dot)com>
To: Silvio Bierman <sbierman(at)jambo-software(dot)com>
Cc: PostgreSQL JDBC <pgsql-jdbc(at)postgresql(dot)org>
Subject: Re: PreparedStatement#setString on non-string parameters
Date: 2005-03-08 12:33:04
Message-ID: (view raw or whole thread)
Lists: pgsql-jdbc

I presume you are talking about setObject ??? I can't find a 
setString(non-string param)


Silvio Bierman wrote:

>Hello all,
>I have just finished a few hours of testing our product that already runs on
>Oracle, SQLServer, MySQL, MaxDB and McKOI on PostgreSQL. I always liked what
>I read about this database apart from the fact that it used to not run
>natively on Windows. Since many of our customers run Windows servers I never
>bothered with PostgreSQL before.
>However, starting with version 8 there is a native Windows version which I
>installed and ran our product on. At first everything was fine and I was
>very impressed with both the performance as the ease of use of the admin
>But when I starting doing writes to the database SQL exceptions started to
>occur. They where all over the application code but where all the same
>error: doing a setString on a numeric parameter. I know this is usually
>suboptimal but since we handle a lot of XML data throughout the (heavily
>distributed) application many numeric values are available as Strings so it
>would be a matter of converting them to numeric values ourselves or letting
>the JDBC driver do that.
>The JDBC drivers we used for the other databasse I mentioned never
>complained. Unfortunately PostgreSQL does. I read somewhere that using the
>pre-version-8 JDBC driver will work with 8 and not show this behaviour, the
>8 driver has deliberately changed the behaviour.
>The JDBC spec requires the driver to attempt a conversion when a
>setString is done on a non-string parameter. This will break a lot of
>conformant code, not only ours. Is there any chance this can be corrected?
>Silvio Bierman
>---------------------------(end of broadcast)---------------------------
>TIP 6: Have you searched our list archives?

Dave Cramer
519 939 0336

In response to


pgsql-jdbc by date

Next:From: Guillaume CottenceauDate: 2005-03-08 12:56:17
Subject: Re: PreparedStatement#setString on non-string parameters
Previous:From: Silvio BiermanDate: 2005-03-08 11:06:10
Subject: PreparedStatement#setString on non-string parameters

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