Re: MySQL v. PostgreSQL

Hallöchen!

Markus Hoenicka writes:

> Torsten Bronger writes:
>
>> However, yesterday I made my Python client Unicode-proof and
>> found out that MySQL has significant trouble with non-ASCII
>> characters in regexps, see
>> <http://bugs.mysql.com/bug.php?id=30241>.  In my opinion this is
>> critical for RefDB applications because it means that queries
>> like ":AU:~Müller" will always fail.
>
> Which mysqld version are you running?

5.0.67, too.

> I cannot reproduce this problem here using the Emacs frontend and
> MySQL 5.0.67. Running a regexp query through said frontend sends
> the following command to a shell:
>
> /home/markus/prog/refdb/refdb/trunk/src/refdbc -c stdout -C getref
> ":AX:~'Mülsch,A'" -E UTF-8 -d stemmat -t ris
>
> This command correctly returns one dataset.

That's really odd.  My complete result was: 

1.  ":AU:~Müller" was not found.

2.  ":AU:~M.ller" was not found.

3.  ":AU:~M....ller" was found.  (It must have been exactly four
    dots.)

4.  ":AU:~ller" was found.

5.  I think that even ":AU:~Müller,A." (which is the complete name)
    was not found.

6.  ":AU:=Müller,A." was found.

With PostgreSQL, all except (3.) were found.  I send in UTF-8
encoding, the "-E" option was always set.  My my.cnf says:

    default-character-set = utf8
    default-storage_engine = innodb
    character-set-server=utf8
    collation-server=utf8_unicode_ci
    init_connect='set collation_connection = utf8_unicode_ci;'

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