Re: UTF-8 collation problem with greek extended characters

2007-02-05 Thread Sven Fuchs
Am 05.02.2007 um 18:11 schrieb Chris White: SELECT * FROM tablename WHERE fieldname LIKE BINARY '[greek small eta]' that *should* ( see disclaimer ;) ) give you what you need Yes, it does. I should have also asked for SELECT DISTINCT fieldname ... in the first place, but looking at your an

Re: UTF-8 collation problem with greek extended characters

2007-02-05 Thread Chris White
Sven Fuchs wrote: These characters are stored/retrieved correctly. But they are wrongly regarded the same character by statements like SELECT * FROM tablename WHERE fieldname LIKE '[greek small eta]' The database's character-set is set to "UTF-8 Unicode (utf8)" and the table's and varchar fie

UTF-8 collation problem with greek extended characters

2007-02-05 Thread Sven Fuchs
MySQL 4.1.22 seems to treat the following characters as equal (comparing them as varchar values): U+03B7 (206 183) greek small letter eta U+1F75 (225 189 181) greek small letter eta with accent oxia U+1FC4 (225 191 135) greek small letter eta with accent persispomeni and accent ypogegrammenti

Re: union/collation problem, error 1267: feature or bug?

2006-01-28 Thread schlubediwup
Hi Gleb, i finally found out a method to be entirely independent from any character-set as well as collation-sequence problem, when forming a UNION, where you occasionnally have to insert place-holders in one of the SELECT statements: as (text, varchar, char) placeholders use NULL instead of "

Re: union/collation problem, error 1267: feature or bug?

2006-01-25 Thread schlubediwup
Hi Gleb, localhost.(none)> show session variables like "%version%"; +-+--+ | Variable_name | Value| +-+--+ | protocol_vers

Re: union/collation problem, error 1267: feature or bug?

2006-01-21 Thread Gleb Paharenko
Hello. Some times the cause of these problems is that some fields have different character sets or it is a bug. I suggest you the following steps: check if the problem still exists in 4.1.16. Then provide the create statements of your tables to the list (they include the character set information)

union/collation problem, error 1267: feature or bug?

2006-01-19 Thread schlubediwup
Hi mysqllers, 1. following installation localhost.addresses2> show global variables like "version%"; +-+--+ | Variable_name | Value| +-+-

Re: Import dump (4.0 > 4.1) and collation problem

2005-06-02 Thread [EMAIL PROTECTED]
Hi, I don't understand very well, what should I do... Does anyone has a step-by-step instructions on how to import a ver. 4.0 DB dump into a 4.1 version ? Thanks for any help Roberto Jobet > > look at automatic character set conversion > http://dev.mysql.com/doc/mysql/en/charset-collation-ch

Re: Import dump (4.0 > 4.1) and collation problem

2005-06-01 Thread mfatene
look at automatic character set conversion http://dev.mysql.com/doc/mysql/en/charset-collation-charset.html mathias Selon [EMAIL PROTECTED]: > Salut, > i don't see what doesn't work ! Where characters are replaced by ?, since you > say that insert,select and import work fine ? is it in the expo

Re: Import dump (4.0 > 4.1) and collation problem

2005-06-01 Thread mfatene
Salut, i don't see what doesn't work ! Where characters are replaced by ?, since you say that insert,select and import work fine ? is it in the export ? see http://dev.mysql.com/doc/mysql/en/upgrading-from-4-0.html for migration. Mathias Selon "[EMAIL PROTECTED]" <[EMAIL PROTECTED]>: > Voilà,

Re: Import dump (4.0 > 4.1) and collation problem

2005-06-01 Thread [EMAIL PROTECTED]
Voilà, Everything works fine: insert, select and importing. I have always the same text: 'Ceci est un test en Français' So what could be the problem ? and how to recover foreign characters ? Thanks Roberto Jobet > i mean : > if you launch : > into into table (toto) values ('Ceci est un test

Re: Import dump (4.0 > 4.1) and collation problem

2005-06-01 Thread mfatene
i mean : if you launch : into into table (toto) values ('Ceci est un test en Français'); then : select toto from table; can you read it correctly ? And if the same row is imported, is there any difference ? A bientôt Mathias Selon "[EMAIL PROTECTED]" <[EMAIL PROTECTED]>: > Salut, > > je vois q

Re: Import dump (4.0 > 4.1) and collation problem

2005-06-01 Thread [EMAIL PROTECTED]
Salut, je vois que tu es français, j'aimerai bien continuer en français mais il vaut mieux en anglais si jamais il y avait quelqu'un avec le même problème ;-) So what I'm trying to achieve is to have UTF-8 databases in order to support multilingual content. But first I have to understand how to

Re: Import dump (4.0 > 4.1) and collation problem

2005-06-01 Thread mfatene
hi, your config supports european charcters : mysql> select * from tst; +--+---+ | a| txt | +--+---+ |1 | Ceci est un test en Français

Import dump (4.0 > 4.1) and collation problem

2005-06-01 Thread [EMAIL PROTECTED]
Hi, I recently upgraded from 4.0 to 4.1 because of the multilingual support. But importing the DB dump into the new 4.1 version all foreign characters (french, spanish, portoguese) have been replaced by ? character... I've been trying to understand the new "collation" feature but i seems quite d

Re: collation problem

2004-06-17 Thread Andrey Kotrekhov
SQL thank you. I found how to set koi8r charset for the server: to set default collation for configure. But how to build mysql client and client library that default client sharset is koi8r? It isn't useful to set this in my.cnf IMHO if I use only one charset for my application. I want something

collation problem

2004-06-05 Thread Andrey Kotrekhov
SQL Hi, all! I have a problem after migration from 4.0.20 to 4.1.2 I have a table `analit`. this is the result of show create table: CREATE TABLE `analit` ( `d` date NOT NULL default '-00-00', `service` binary(16) NOT NULL default '', `price` char(50) NOT NULL default '', `type` char(50