-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
robert kuzelj wrote:
> hi mark,
>
>> If you specify UTF-8 as the characterEncoding connection property, then
>> that is the transform that is used from client -> server. The transform
>> that is used from server -> client is whatever character set the column
>> in the table is set to when you created the table (or conversely if you
>> use cast/convert in SQL to change it to some other character set).
> so you say ;-) and i still have my doubts about it (but more on that
> later). what i have done now is to extract a junit test as requested
> by you (TestUTF8.java). i executed the test on two different machines
> now (suse linux 9.0 and WinXp both running mysql 4.1.1-a). as you would
> expect the tests run perfectly well.
What happens if you explicitly specify the table character set to be
'utf-8'? (i.e. you're relying on the database default character set to
take care of that for you right now)...
'CREATE TABLE foo CHARACTER SET utf8'
All I can say is that with the testcase I posted, it is shown that what
you put in in UTF-8 format is what you get out, byte-for-byte with no
double transformations (getBytes() _never_ uses charset information, so
comparing ResultSet.getBytes() with a String.getBytes("utf-8") shows
that the data is retrieved in UTF-8 form).
-Mark
- --
Mr. Mark Matthews
MySQL AB, Software Development Manager, J2EE and Windows Platforms
Office: +1 708 332 0507
www.mysql.com
MySQL Guide to Lower TCO
http://www.mysql.com/it-resources/white-papers/tco.php
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (MingW32)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFAtiEZtvXNTca6JD8RAtYAAKCmKK/6VQr5W7X4Pz299zufHrDdtwCdHddv
Amm4puj9SmCSuuQzMPfBZjw=
=rPtF
-----END PGP SIGNATURE-----
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
