Re: FW: PreparedStatement#setString on non-string parameters

Silvio Bierman wrote:

> Either the JDBC drivers for the databases I mentioned earlier do the
> conversion or the database backends do it on the server side. Any way, this
> works in all cases. PostgreSQL is the first database to break our
> application due to this behaviour. We have had problems on earlier versions
> of MySQL because of lack of subselect support etc. but never these issues.

I'd suggest using CAST in your SQL -- that in theory should work
everywhere and reflects your application's intent (to interpret a string
as a numeric value).

The problem with reverting to the old way of doing parameters (direct
text substitution into the query) is that we cannot take advantage of
most of the new stuff in the V3 protocol -- that means no server-side
prepared statement reuse, no low-overhead transfer of large parameters,
and reduced support for cursor-based resultsets.

-O