Subject Re: JDBC driver problem
Author Roman Rokytskyy
Hi Nickolay,

> --- 2004-08-03 11:50:37.000000000 +0400
> +++ 2004-07-08 14:10:47.000000000 +0400

Confirmed. Will be fixed today.

> Additinally, this guy is unhappy that setCharacterStream apparently
> uses JVM encoding for all blobs.

> He changed this method to use something like
> OutputStreamWriter osw = new OutputStreamWriter(os, javaEncoding);
> to be consistent with setString() logic.

Makes sense. I will add this before the release.

> His final comment was:

I do not agree with his comment. He suggests to use either database or
column encoding when reading the content of the BLOB field. I believe that
the client encoding should be used (not the JVM encoding as it is now) and
server must convert the text blobs (sub_type 1) into this encoding. If
server does not do this, this is a bug and must be fixed.