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

"Silvio Bierman" <sbierman 'at' jambo-software.com> writes:

> 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

But you understand it's not breaking the JDBC spec, though.

> of MySQL because of lack of subselect support etc. but never these issues.
>
> I really love what I have seen of PostgreSQL until now and I am seriously
> considering making it our preferred database backend. The ability to run on
> both Linux and Windows is great, performance is excellent (I tried a quite
> large database) even when I am still inserting my GUID keys as varchar data
> and the admin tool is very good also.
>
> Telling my users to use an old JDBC driver is not an option though...

But telling the developers to follow the JDBC specs is definitely
an option :). Understand me: I know that there can be a real pile
of existing code that did run before, and is broken now by this
change. However, you cannot ask developers implementing a
specification to intentionally break the specification because
others drivers and old version did so.

--
Guillaume Cottenceau