Hi!
I communicated with Marco Paskamp some weeks ago about something I
noticed when testing my application: http://lists.mysql.com/maxdb/28061
In an off-list discussion we found out that the JDBC driver throws an
exception when converting a unicode character for an ASCII/latin1-db.
I contacted Marco off-list for the following problem but go no response, so:
my test runs further now but fails when working with ASCII character 181
(micro sign, mju). here is statement and exception:
com.sap.dbtech.jdbc.exceptions.DatabaseException: [-8044]: Conversion
for character set value impossible
SELECT DISTINCT main.oid FROM users main WHERE UPPER(main.phone) LIKE
UPPER('%ยต%') ESCAPE '\'
previous to this statement some other tests with = and like operators
succeeded. i guess something realizes that there is no UPPER() for this
character in latin1 and fails.
other DBs/drivers (mysql, db2, ora, postgresql, sapdb) behave
differently: they just leave the character as is and continue. I think
this is what should happen.
the rest of my testcase continues and encounters the same problem with
character 255.
this is all with JDBC driver MySQL MaxDB, 7.6.0 Build
030-000-005-567 and server 7.6.00 BUILD 027-121-124-939 on Linux.
thanks for any comment,
Raimund
--
Pinuts media+science GmbH http://www.pinuts.de
Raimund Jacob [EMAIL PROTECTED]
Krausenstr. 9-10 voice : +49 30 59 00 90 322
10117 Berlin fax : +49 30 59 00 90 390
Germany
--
MaxDB Discussion Mailing List
For list archives: http://lists.mysql.com/maxdb
To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
