Mailing List
Home
Forum Home
MySQL General - General MySQL discussion
MaxDB - Everything about MaxDB, formerly known as SAP DB
MySQL++ - Programming with the C++ API to MySQL
ODBC - ODBC with the MySQL Connector/ODBC driver
MySQL on Win32 - Runing MySQL on Windows 9x/Me/NT/2000/XP
Java Help - Mostly related to the MySQL Connector/J driver
Perl - Perl support for MySQL with DBI and DBD::mysql
GUI - MySQL GUI Tools
Announcement
Subjects
mysql openssl Question
mysql:it 's a db not a dbms how it 's possible?!
Does the binary log enabling affect the MySQL performances?
Strange behavior, Table Level Permission
FULLTEXT query format question
Preventing Duplicate Entries
Comparing and writing out BLOBS
Executing MySQL Commands From Within C Program
Can 't access mysql after kernel upgrade
Mysql 4 0 Oracle Stored Procedure Trigger Conversion
Downgrade Mysql from 4 to 3 23
MySQL Cluster Software
mysql test 4 1 fails with the gis test
ERROR 2002: Can 't connect to local MySQL server through socket
Getting Identity after INSERT
Update one field with more fields from another table
ERROR 1045: Access denied for user: 'root@localhost ' (Using
password: NO)
mysql have same function mthod as Oracle decode()
 
Again strange behaviour with JDBC driver

Again strange behaviour with JDBC driver

2007-01-19       - By Raimund Jacob

 Back
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                             Raimund.Jacob@(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/maxdb?unsub=mysql@(protected)