hi mark,
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'
the same.
All I can say is that with the testcase I posted, it is shown
-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
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
us
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
robert kuzelj wrote:
> hallo mark,
>
>> Hopefully the following JUnit testcase helps show that your problem
>> doesn't exist at the JDBC level. It creates a UTF-8 connection to
>> MySQL-4.1.2, stores UTF-8 encoded strings directly and by prepared
>> s
hallo mark,
Hopefully the following JUnit testcase helps show that your problem
doesn't exist at the JDBC level. It creates a UTF-8 connection to
MySQL-4.1.2, stores UTF-8 encoded strings directly and by prepared
statements, retrieves them, compares to original as strings, and
byte-for-byte using t
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
robert kuzelj wrote:
> hi mark,
>
> > However, once you start displaying things on the console, all bets are
> > off...because your console needs to understand UTF-8 as well, so using
> > the 'eyeball' method of testing won't work too well here.
>
hi mark,
> However, once you start displaying things on the console, all bets are
> off...because your console needs to understand UTF-8 as well, so using
> the 'eyeball' method of testing won't work too well here.
in principle i agree with you. but only having java tests is simply
not enough. i ha
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
robert kuzelj wrote:
> [code]
> 18String family = new String(rs.getBytes("FAMILY_NAME"));
> 19String given = new String(rs.getBytes("GIVEN_NAME"));
> [/code]
>
> [result]
> [java] .Käßsel - Böb
> [java] Ægÿl - Àlbért
>
seems like my problem is not necesseraly tied to mysql.
at least i can reproduce all of this also with postgres.
instead of writing to the database i tried to read from
it (after inserting data via the following simple script on the
commandline)
[code]
[EMAIL PROTECTED]:> more example_insert.sql
in
hi Yiannis,
Try changing Eclipse's setting to saving the files as UTF-8 and also force the
JVM to the UTF-8 file encoding.
eclipse is already set to only write UTF-8. but how should i force
the jvm to work with that encoding?
ciao robertj
smime.p7s
Description: S/MIME Cryptographic Signature
Try changing Eclipse's setting to saving the files as UTF-8 and also force the
JVM to the UTF-8 file encoding.
-Original Message-
From: robert kuzelj [mailto:[EMAIL PROTECTED]
Sent: 26 May 2004 15:01
To: [EMAIL PROTECTED]
Subject: UTF-8 settings and woes
hi,
i am trying to write
hi,
i am trying to write utf-8 data via java into sql but
it wont work as expected.
first my setup
- suse 9.0
- kde 3.2
mysql> SHOW VARIABLES LIKE 'char%';
+--++
| Variable_name| Value |
+--
12 matches
Mail list logo
