Re: MySQL v. PostgreSQL

Hallöchen!

Markus Hoenicka writes:

> [...]
>
> [...] The weird thing is that this should cause an iconv error, as
> "UTF8" is not a valid encoding name supported by iconv. What does
>
> iconv -l|grep -i utf8
>
> return on your system?

bronger@wilson:~$ iconv -l|grep -i utf8
ISO-10646/UTF8/
UTF8//

> [...]
>
> Did you check those datasets which you inserted when creating the
> above logs? Is it possible that you changed your setup at some
> point, and only datasets fail which you added before that point?

No, it's very well reproducible here.  The Umlauts are
double-encoded in the MySQL database (I can see it in the MySQL
admin tool).  On the other hand, they are correct in RefDB's log
output.  So there are two possibilities:

-  RefDB encodes the UTF-8 data that it gets from me again, but it
   does so after it prints it to the log output, or

-  RefDB passes UTF-8 data to the database and tells MySQL that it's
   Latin-1.

If I correct the data in the MySQL table, RefDB sends Latin-1 data
to me.

Tschö,
Torsten.

-- 
Torsten Bronger, aquisgrana, europa vetus
                   Jabber ID: [email protected]


------------------------------------------------------------------------------
Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA
-OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise
-Strategies to boost innovation and cut costs with open source participation
-Receive a $600 discount off the registration fee with the source code: SFAD
http://p.sf.net/sfu/XcvMzF8H