On 06.03.2008 15:15 CE(S)T, Paul DuBois wrote:
Here's some advice from Alexander Barkov:
You might be able to use a particular collation to achieve what you want.
For example, latin1_general_ci.
You can take a look at its collation chart here:
http://www.collation-charts.org/mysql60/mysql604.lat
On 03.03.2008 23:17 CE(S)T, Anders Karlsson wrote:
And you are right of course, you may use the COLLATE keyword also,
to enforce a certain collation, although if you want BINARY, I think
using BINARY might be slightly more effective.
I was also considering compatibility with other DBMS. At
Yves!
OK. I agree I don't like this much myself, but we have to live with
the multi-lingual aspect of UNICODE. Or rather, we have to agree to be
either multi-lingual, and have the cons and pros of that (using
UNICODE), or ignore UNICODE and have binary collations etc. And
collation also de
yves
when creating a varchar field in table creation, use the binary.
that way, selection is exact. always.
david
-Original Message-
From: Yves Goergen [mailto:[EMAIL PROTECTED]
Sent: Monday, March 03, 2008 1:44 PM
To: Anders Karlsson
Cc: MySQL
Subject: Re: Unicode sorting and binary
On 03.03.2008 10:27 CE(S)T, Anders Karlsson wrote:
> [a lot about why sorting unicode is complicated]
If you want to
accknowledge exact matching, and say any character, accented / unlauted
etc, is different from any other character, specifiy a binary comparison:
SELECT * FROM phonebook WHERE BI
Yves!
This is a complicated matter alright, but it is a complicated
problem to solve here also. Your statement about characters being the
same isn't really correct. To take an example: Let's assume you were
doing a phonebook, in print, of all people in the world. How would you
sort that? A
Hello,
I've just read through the MySQL documentation about Unicode support,
collations and how it affects sorting and comparison of strings. And I
find it horrible, at least. I feel like I'm back in the MySQL 3.x days
where I used UTF-8 in my application and MySQL treated it binary. The
only
