Re: UTF-8 collation problem with greek extended characters
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 answer and asking Google I've already seen that MySQL knows DISTINCT BINARY also. Thanks a million, Chris! -- sven fuchs fon: +49 (58 45) 98 89 58 artweb design fax: +49 (58 45) 98 89 57 breite straße 65www: http://www.artweb-design.de de-29468 bergen mail: [EMAIL PROTECTED] -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: UTF-8 collation problem with greek extended characters
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 field's collation is set "utf8_unicode_ci". Is there anything I can do to have MySQL distinguish these characters? DISCLAIMER: not tested try something like: SELECT * FROM tablename WHERE fieldname LIKE BINARY '[greek small eta]' that *should* ( see disclaimer ;) ) give you what you need -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
UTF-8 collation problem with greek extended characters
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 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 field's collation is set "utf8_unicode_ci". Is there anything I can do to have MySQL distinguish these characters? (mysql --version is Ver 14.7 Distrib 4.1.22, for apple-darwin8.8.1 (i686) using EditLine wrapper) Thanks in advance! -- sven fuchs fon: +49 (58 45) 98 89 58 artweb design fax: +49 (58 45) 98 89 57 breite straße 65www: http://www.artweb-design.de de-29468 bergen mail: [EMAIL PROTECTED] -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: union/collation problem, error 1267: feature or bug?
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 "" or '' if your application permits it. thanks for your suggestion an help. suomi -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: union/collation problem, error 1267: feature or bug?
Hi Gleb, localhost.(none)> show session variables like "%version%"; +-+--+ | Variable_name | Value| +-+--+ | protocol_version| 10 | | version | 4.1.16-standard | | version_comment | MySQL Community Edition - Standard (GPL) | | version_compile_machine | i686 | | version_compile_os | pc-linux-gnu | +-+--+ 5 rows in set (0.00 sec) localhost.(none)> with the new version , in a first view, the problem i reported on 20. january 2006, does not occur anymore. thanks for your suggestion an help. suomi -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: union/collation problem, error 1267: feature or bug?
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). See: http://dev.mysql.com/doc/refman/4.1/en/charset-collation-charset.html schlubediwup wrote: > Hi mysqllers, > > 1. following installation > > > localhost.addresses2> show global variables like "version%"; > +-+--+ > | Variable_name | Value| > +-+--+ > | version | 4.1.14-standard | > | version_comment | MySQL Community Edition - Standard (GPL) | > | version_compile_machine | i686 | > | version_compile_os | pc-linux-gnu | > +-+--+ > 4 rows in set (0.00 sec) > > localhost.addresses2> > > > > 2. following two tables are involved: > > localhost.addresses2> describe contacts2; > +--+--+--+-+---++ > > | Field| Type | Null | Key | Default | > Extra | > +--+--+--+-+---++ > > | name | text | YES | | NULL > || > | firm | text | YES | | NULL > || > | title| text | YES | | NULL > || > | phone| text | YES | | NULL > || > | mail | text | YES | | NULL > || > | comment | text | YES | | NULL > || > | status | text | YES | | NULL > || > | url | text | YES | | NULL > || > | businesscategory | text | YES | | NULL > || > | address | text | YES | | NULL > || > | kanton | text | YES | | NULL > || > | addon| text | YES | | NULL > || > | givenname| text | YES | | NULL > || > | history | text | YES | | NULL > || > | favorit | text | YES | | NULL > || > | last_update | timestamp| YES | | CURRENT_TIMESTAMP > || > | counter | int(10) unsigned | | PRI | NULL | > auto_increment | > +--+--+--+-+---++ > > 17 rows in set (0.00 sec) > > localhost.addresses2> > > > localhost.addresses2> describe tasks2; > +--+--+--+-+---++ > > | Field| Type | Null | Key | Default | > Extra | > +--+--+--+-+---++ > > | task_name| text | YES | | NULL > || > | actiony | text | YES | | NULL > || > | date_start | date | YES | | NULL > || > | date_end | date | YES | | NULL > || > | date_last_action | date | YES | | NULL > || > | date_next_action | date | YES | | NULL > || > | start_time | time | YES | | NULL > || > | end_time | time | YES | | NULL > || > | task_address | text | YES | | NULL > || > | task_comment | text | YES | | NULL > || > | task_responsible | text | YES | | NULL > || > | project | text | YES | | NULL > || > | task_history | text | YES | | NULL > || > | task_last_update | timestamp| YES | | CURRENT_TIMESTAMP > || > | contact_link | int(11) | YES | | NULL
union/collation problem, error 1267: feature or bug?
Hi mysqllers, 1. following installation localhost.addresses2> show global variables like "version%"; +-+--+ | Variable_name | Value| +-+--+ | version | 4.1.14-standard | | version_comment | MySQL Community Edition - Standard (GPL) | | version_compile_machine | i686 | | version_compile_os | pc-linux-gnu | +-+--+ 4 rows in set (0.00 sec) localhost.addresses2> 2. following two tables are involved: localhost.addresses2> describe contacts2; +--+--+--+-+---++ | Field| Type | Null | Key | Default | Extra | +--+--+--+-+---++ | name | text | YES | | NULL || | firm | text | YES | | NULL || | title| text | YES | | NULL || | phone| text | YES | | NULL || | mail | text | YES | | NULL || | comment | text | YES | | NULL || | status | text | YES | | NULL || | url | text | YES | | NULL || | businesscategory | text | YES | | NULL || | address | text | YES | | NULL || | kanton | text | YES | | NULL || | addon| text | YES | | NULL || | givenname| text | YES | | NULL || | history | text | YES | | NULL || | favorit | text | YES | | NULL || | last_update | timestamp| YES | | CURRENT_TIMESTAMP || | counter | int(10) unsigned | | PRI | NULL | auto_increment | +--+--+--+-+---++ 17 rows in set (0.00 sec) localhost.addresses2> localhost.addresses2> describe tasks2; +--+--+--+-+---++ | Field| Type | Null | Key | Default | Extra | +--+--+--+-+---++ | task_name| text | YES | | NULL || | actiony | text | YES | | NULL || | date_start | date | YES | | NULL || | date_end | date | YES | | NULL || | date_last_action | date | YES | | NULL || | date_next_action | date | YES | | NULL || | start_time | time | YES | | NULL || | end_time | time | YES | | NULL || | task_address | text | YES | | NULL || | task_comment | text | YES | | NULL || | task_responsible | text | YES | | NULL || | project | text | YES | | NULL || | task_history | text | YES | | NULL || | task_last_update | timestamp| YES | | CURRENT_TIMESTAMP || | contact_link | int(11) | YES | | NULL || | task_counter | int(10) unsigned | | PRI | NULL | auto_increment | +--+--+--+-+---++ 16 rows in set (0.00 sec) localhost.addresses2> 3. following character-sets and collations: localhost.addresses2> show session variables like "character%"; +--++ | Variable_name| Value | +--++ | character_set_client | utf8
Re: Import dump (4.0 > 4.1) and collation problem
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-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 export ?
> >
> > see http://dev.mysql.com/doc/mysql/en/upgrading-from-4-0.html for migration.
> >
> >
> > Mathias
> >
> > Selon "[EMAIL PROTECTED]" <[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 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 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 recover foreign characters in my
> > > DB.
> > > > >
> > > > > What do you mean by: "try some inserts to see if it is an import
> > problem
> > > " or
> > > > > "just the client display" ?
> > > > >
> > > > > Merci d'avance
> > > > >
> > > > > Roberto Jobet
> > > > >
> > > > >
> > > > > > hi,
> > > > > > your config supports european characters :
> > > > > >
> > > > > > mysql> select * from tst;
> > > > > > +--+---+
> > > > > > | a| txt |
> > > > > > +--+---+
> > > > > > |1 | Ceci est un test en Français |
> > > > > > |1 | se facilitará el conocimiento de la evolución del |
> > > > > > +--+---+
> > > > > > 2 rows in set (0.00 sec)
> > > > > >
> > > > > > mysql> show variables like '%coll%';
> > > > > > +--+---+
> > > > > > | Variable_name| Value |
> > > > > > +--+---+
> > > > > > | collation_connection | latin1_swedish_ci |
> > > > > > | collation_database | latin1_swedish_ci |
> > > > > > | collation_server | latin1_swedish_ci |
> > > > > > +--+---+
> > > > > > 3 rows in set (0.00 sec)
> > > > > >
> > > > > >
> > > > > > have you tried some inserts to see if it is an import problem, or
> > just
> > > the
> > > > > > client display ?
> > > > > >
> > > > > > Mathias
> > > > > >
> > > > > > Selon "[EMAIL PROTECTED]" <[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
> > > > > > > difficult to setup.
> > > > > > >
> > > > > > > Anybody has already faced this problem ?
> > > > > > >
> > > > > > > Here's my current configuration:
> > > > > > >
> > > > > > > 1) my.cnf (only the mysqld section)
> > > > > > >
> > > > > > > [mysqld]
> > > > > > > user= mysql
> > > > > > > pid-file= /var/run/mysqld/mysqld.pid
> > > > > > > socket = /var/run/mysqld/mysqld.sock
> > > > > > > port= 3306
> > > > > > > # Both location gets rotated by the cronjob.
> > > > > > > #log= /var/log/mysql.log
> > > > > > > log = /var/log/mysql/mysql.log
> > > > > > > basedir = /usr
> > > > > > > datadir = /db
> > > > > > > tmpdir = /tmp
> > > > > > > language= /usr/share/mysql/english
> > > > > > >
> > > > > > > 2) Output show variables like '%char%';
> > > > > > >
> > > > > > > character_set_client utf8
> > > > > > > character_set_connection utf8
> > > > > > > character_set_database latin1
> > > > > > > character_set_results utf8
> > > > > > > character_set_server latin1
> > > > > > > character_set_system
Re: Import dump (4.0 > 4.1) and collation problem
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 export ?
>
> see http://dev.mysql.com/doc/mysql/en/upgrading-from-4-0.html for migration.
>
>
> Mathias
>
> Selon "[EMAIL PROTECTED]" <[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 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 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 recover foreign characters in my
> > DB.
> > > >
> > > > What do you mean by: "try some inserts to see if it is an import
> problem
> > " or
> > > > "just the client display" ?
> > > >
> > > > Merci d'avance
> > > >
> > > > Roberto Jobet
> > > >
> > > >
> > > > > hi,
> > > > > your config supports european characters :
> > > > >
> > > > > mysql> select * from tst;
> > > > > +--+---+
> > > > > | a| txt |
> > > > > +--+---+
> > > > > |1 | Ceci est un test en Français |
> > > > > |1 | se facilitará el conocimiento de la evolución del |
> > > > > +--+---+
> > > > > 2 rows in set (0.00 sec)
> > > > >
> > > > > mysql> show variables like '%coll%';
> > > > > +--+---+
> > > > > | Variable_name| Value |
> > > > > +--+---+
> > > > > | collation_connection | latin1_swedish_ci |
> > > > > | collation_database | latin1_swedish_ci |
> > > > > | collation_server | latin1_swedish_ci |
> > > > > +--+---+
> > > > > 3 rows in set (0.00 sec)
> > > > >
> > > > >
> > > > > have you tried some inserts to see if it is an import problem, or
> just
> > the
> > > > > client display ?
> > > > >
> > > > > Mathias
> > > > >
> > > > > Selon "[EMAIL PROTECTED]" <[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
> > > > > > difficult to setup.
> > > > > >
> > > > > > Anybody has already faced this problem ?
> > > > > >
> > > > > > Here's my current configuration:
> > > > > >
> > > > > > 1) my.cnf (only the mysqld section)
> > > > > >
> > > > > > [mysqld]
> > > > > > user= mysql
> > > > > > pid-file= /var/run/mysqld/mysqld.pid
> > > > > > socket = /var/run/mysqld/mysqld.sock
> > > > > > port= 3306
> > > > > > # Both location gets rotated by the cronjob.
> > > > > > #log= /var/log/mysql.log
> > > > > > log = /var/log/mysql/mysql.log
> > > > > > basedir = /usr
> > > > > > datadir = /db
> > > > > > tmpdir = /tmp
> > > > > > language= /usr/share/mysql/english
> > > > > >
> > > > > > 2) Output show variables like '%char%';
> > > > > >
> > > > > > character_set_client utf8
> > > > > > character_set_connection utf8
> > > > > > character_set_database latin1
> > > > > > character_set_results utf8
> > > > > > character_set_server latin1
> > > > > > character_set_system utf8
> > > > > > character_sets_dir /usr/share/mysql/charsets/
> > > > > >
> > > > > > 3) Out put show variables like '%coll%';
> > > > > >
> > > > > > collation_connection utf8_general_ci
> > > > > > collation_database latin1_swedish_ci
> > > > > > collation_server latin1_swedish_ci
> > > > > >
> > > > > > Thanks for any help
> > > > > >
> > > > > > Regards
> > > > > >
> > > > > > Roberto Jobet
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
Re: Import dump (4.0 > 4.1) and collation problem
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à,
>
> 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 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 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 recover foreign characters in my
> DB.
> > >
> > > What do you mean by: "try some inserts to see if it is an import problem
> " or
> > > "just the client display" ?
> > >
> > > Merci d'avance
> > >
> > > Roberto Jobet
> > >
> > >
> > > > hi,
> > > > your config supports european characters :
> > > >
> > > > mysql> select * from tst;
> > > > +--+---+
> > > > | a| txt |
> > > > +--+---+
> > > > |1 | Ceci est un test en Français |
> > > > |1 | se facilitará el conocimiento de la evolución del |
> > > > +--+---+
> > > > 2 rows in set (0.00 sec)
> > > >
> > > > mysql> show variables like '%coll%';
> > > > +--+---+
> > > > | Variable_name| Value |
> > > > +--+---+
> > > > | collation_connection | latin1_swedish_ci |
> > > > | collation_database | latin1_swedish_ci |
> > > > | collation_server | latin1_swedish_ci |
> > > > +--+---+
> > > > 3 rows in set (0.00 sec)
> > > >
> > > >
> > > > have you tried some inserts to see if it is an import problem, or just
> the
> > > > client display ?
> > > >
> > > > Mathias
> > > >
> > > > Selon "[EMAIL PROTECTED]" <[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
> > > > > difficult to setup.
> > > > >
> > > > > Anybody has already faced this problem ?
> > > > >
> > > > > Here's my current configuration:
> > > > >
> > > > > 1) my.cnf (only the mysqld section)
> > > > >
> > > > > [mysqld]
> > > > > user= mysql
> > > > > pid-file= /var/run/mysqld/mysqld.pid
> > > > > socket = /var/run/mysqld/mysqld.sock
> > > > > port= 3306
> > > > > # Both location gets rotated by the cronjob.
> > > > > #log= /var/log/mysql.log
> > > > > log = /var/log/mysql/mysql.log
> > > > > basedir = /usr
> > > > > datadir = /db
> > > > > tmpdir = /tmp
> > > > > language= /usr/share/mysql/english
> > > > >
> > > > > 2) Output show variables like '%char%';
> > > > >
> > > > > character_set_client utf8
> > > > > character_set_connection utf8
> > > > > character_set_database latin1
> > > > > character_set_results utf8
> > > > > character_set_server latin1
> > > > > character_set_system utf8
> > > > > character_sets_dir /usr/share/mysql/charsets/
> > > > >
> > > > > 3) Out put show variables like '%coll%';
> > > > >
> > > > > collation_connection utf8_general_ci
> > > > > collation_database latin1_swedish_ci
> > > > > collation_server latin1_swedish_ci
> > > > >
> > > > > Thanks for any help
> > > > >
> > > > > Regards
> > > > >
> > > > > Roberto Jobet
> > >
> > >
> > >
> > >
> > >
> > > 6X velocizzare la tua navigazione a 56k? 6X Web Accelerator di Libero!
> > > Scaricalo su INTERNET GRATIS 6X http://www.libero.it
> > >
> > >
> > >
> > > --
> > > MySQL General Mailing List
> > > For list archives: http://lists.mysql.com/mysql
> > > To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
> > >
> > >
> >
> >
> >
>
>
>
>
> 6X velocizzare la tua navigazione a 56k? 6X Web Ac
Re: Import dump (4.0 > 4.1) and collation problem
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 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 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 recover foreign characters in my DB.
> >
> > What do you mean by: "try some inserts to see if it is an import problem "
> > or
> > "just the client display" ?
> >
> > Merci d'avance
> >
> > Roberto Jobet
> >
> >
> > > hi,
> > > your config supports european characters :
> > >
> > > mysql> select * from tst;
> > > +--+---+
> > > | a| txt |
> > > +--+---+
> > > |1 | Ceci est un test en Français |
> > > |1 | se facilitará el conocimiento de la evolución del |
> > > +--+---+
> > > 2 rows in set (0.00 sec)
> > >
> > > mysql> show variables like '%coll%';
> > > +--+---+
> > > | Variable_name| Value |
> > > +--+---+
> > > | collation_connection | latin1_swedish_ci |
> > > | collation_database | latin1_swedish_ci |
> > > | collation_server | latin1_swedish_ci |
> > > +--+---+
> > > 3 rows in set (0.00 sec)
> > >
> > >
> > > have you tried some inserts to see if it is an import problem, or just the
> > > client display ?
> > >
> > > Mathias
> > >
> > > Selon "[EMAIL PROTECTED]" <[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
> > > > difficult to setup.
> > > >
> > > > Anybody has already faced this problem ?
> > > >
> > > > Here's my current configuration:
> > > >
> > > > 1) my.cnf (only the mysqld section)
> > > >
> > > > [mysqld]
> > > > user= mysql
> > > > pid-file= /var/run/mysqld/mysqld.pid
> > > > socket = /var/run/mysqld/mysqld.sock
> > > > port= 3306
> > > > # Both location gets rotated by the cronjob.
> > > > #log= /var/log/mysql.log
> > > > log = /var/log/mysql/mysql.log
> > > > basedir = /usr
> > > > datadir = /db
> > > > tmpdir = /tmp
> > > > language= /usr/share/mysql/english
> > > >
> > > > 2) Output show variables like '%char%';
> > > >
> > > > character_set_client utf8
> > > > character_set_connection utf8
> > > > character_set_database latin1
> > > > character_set_results utf8
> > > > character_set_server latin1
> > > > character_set_system utf8
> > > > character_sets_dir /usr/share/mysql/charsets/
> > > >
> > > > 3) Out put show variables like '%coll%';
> > > >
> > > > collation_connection utf8_general_ci
> > > > collation_database latin1_swedish_ci
> > > > collation_server latin1_swedish_ci
> > > >
> > > > Thanks for any help
> > > >
> > > > Regards
> > > >
> > > > Roberto Jobet
> >
> >
> >
> >
> >
> > 6X velocizzare la tua navigazione a 56k? 6X Web Accelerator di Libero!
> > Scaricalo su INTERNET GRATIS 6X http://www.libero.it
> >
> >
> >
> > --
> > MySQL General Mailing List
> > For list archives: http://lists.mysql.com/mysql
> > To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
> >
> >
>
>
>
6X velocizzare la tua navigazione a 56k? 6X Web Accelerator di Libero!
Scaricalo su INTERNET GRATIS 6X http://www.libero.it
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: Import dump (4.0 > 4.1) and collation problem
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 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 recover foreign characters in my DB.
>
> What do you mean by: "try some inserts to see if it is an import problem " or
> "just the client display" ?
>
> Merci d'avance
>
> Roberto Jobet
>
>
> > hi,
> > your config supports european characters :
> >
> > mysql> select * from tst;
> > +--+---+
> > | a| txt |
> > +--+---+
> > |1 | Ceci est un test en Français |
> > |1 | se facilitará el conocimiento de la evolución del |
> > +--+---+
> > 2 rows in set (0.00 sec)
> >
> > mysql> show variables like '%coll%';
> > +--+---+
> > | Variable_name| Value |
> > +--+---+
> > | collation_connection | latin1_swedish_ci |
> > | collation_database | latin1_swedish_ci |
> > | collation_server | latin1_swedish_ci |
> > +--+---+
> > 3 rows in set (0.00 sec)
> >
> >
> > have you tried some inserts to see if it is an import problem, or just the
> > client display ?
> >
> > Mathias
> >
> > Selon "[EMAIL PROTECTED]" <[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
> > > difficult to setup.
> > >
> > > Anybody has already faced this problem ?
> > >
> > > Here's my current configuration:
> > >
> > > 1) my.cnf (only the mysqld section)
> > >
> > > [mysqld]
> > > user= mysql
> > > pid-file= /var/run/mysqld/mysqld.pid
> > > socket = /var/run/mysqld/mysqld.sock
> > > port= 3306
> > > # Both location gets rotated by the cronjob.
> > > #log= /var/log/mysql.log
> > > log = /var/log/mysql/mysql.log
> > > basedir = /usr
> > > datadir = /db
> > > tmpdir = /tmp
> > > language= /usr/share/mysql/english
> > >
> > > 2) Output show variables like '%char%';
> > >
> > > character_set_client utf8
> > > character_set_connection utf8
> > > character_set_database latin1
> > > character_set_results utf8
> > > character_set_server latin1
> > > character_set_system utf8
> > > character_sets_dir /usr/share/mysql/charsets/
> > >
> > > 3) Out put show variables like '%coll%';
> > >
> > > collation_connection utf8_general_ci
> > > collation_database latin1_swedish_ci
> > > collation_server latin1_swedish_ci
> > >
> > > Thanks for any help
> > >
> > > Regards
> > >
> > > Roberto Jobet
>
>
>
>
>
> 6X velocizzare la tua navigazione a 56k? 6X Web Accelerator di Libero!
> Scaricalo su INTERNET GRATIS 6X http://www.libero.it
>
>
>
> --
> MySQL General Mailing List
> For list archives: http://lists.mysql.com/mysql
> To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
>
>
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: Import dump (4.0 > 4.1) and collation problem
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 recover foreign characters in my DB. What do you mean by: "try some inserts to see if it is an import problem " or "just the client display" ? Merci d'avance Roberto Jobet > hi, > your config supports european characters : > > mysql> select * from tst; > +--+---+ > | a| txt | > +--+---+ > |1 | Ceci est un test en Français | > |1 | se facilitará el conocimiento de la evolución del | > +--+---+ > 2 rows in set (0.00 sec) > > mysql> show variables like '%coll%'; > +--+---+ > | Variable_name| Value | > +--+---+ > | collation_connection | latin1_swedish_ci | > | collation_database | latin1_swedish_ci | > | collation_server | latin1_swedish_ci | > +--+---+ > 3 rows in set (0.00 sec) > > > have you tried some inserts to see if it is an import problem, or just the > client display ? > > Mathias > > Selon "[EMAIL PROTECTED]" <[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 > > difficult to setup. > > > > Anybody has already faced this problem ? > > > > Here's my current configuration: > > > > 1) my.cnf (only the mysqld section) > > > > [mysqld] > > user= mysql > > pid-file= /var/run/mysqld/mysqld.pid > > socket = /var/run/mysqld/mysqld.sock > > port= 3306 > > # Both location gets rotated by the cronjob. > > #log= /var/log/mysql.log > > log = /var/log/mysql/mysql.log > > basedir = /usr > > datadir = /db > > tmpdir = /tmp > > language= /usr/share/mysql/english > > > > 2) Output show variables like '%char%'; > > > > character_set_client utf8 > > character_set_connection utf8 > > character_set_database latin1 > > character_set_results utf8 > > character_set_server latin1 > > character_set_system utf8 > > character_sets_dir /usr/share/mysql/charsets/ > > > > 3) Out put show variables like '%coll%'; > > > > collation_connection utf8_general_ci > > collation_database latin1_swedish_ci > > collation_server latin1_swedish_ci > > > > Thanks for any help > > > > Regards > > > > Roberto Jobet 6X velocizzare la tua navigazione a 56k? 6X Web Accelerator di Libero! Scaricalo su INTERNET GRATIS 6X http://www.libero.it -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: Import dump (4.0 > 4.1) and collation problem
hi, your config supports european charcters : mysql> select * from tst; +--+---+ | a| txt | +--+---+ |1 | Ceci est un test en Français | |1 | se facilitará el conocimiento de la evolución del | +--+---+ 2 rows in set (0.00 sec) mysql> show variables like '%coll%'; +--+---+ | Variable_name| Value | +--+---+ | collation_connection | latin1_swedish_ci | | collation_database | latin1_swedish_ci | | collation_server | latin1_swedish_ci | +--+---+ 3 rows in set (0.00 sec) have you tried some inserts to see if it is an import problem, or just the client display ? Mathias Selon "[EMAIL PROTECTED]" <[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 > difficult to setup. > > Anybody has already faced this problem ? > > Here's my current configuration: > > 1) my.cnf (only the mysqld section) > > [mysqld] > user= mysql > pid-file= /var/run/mysqld/mysqld.pid > socket = /var/run/mysqld/mysqld.sock > port= 3306 > # Both location gets rotated by the cronjob. > #log= /var/log/mysql.log > log = /var/log/mysql/mysql.log > basedir = /usr > datadir = /db > tmpdir = /tmp > language= /usr/share/mysql/english > > 2) Output show variables like '%char%'; > > character_set_client utf8 > character_set_connection utf8 > character_set_database latin1 > character_set_results utf8 > character_set_server latin1 > character_set_system utf8 > character_sets_dir /usr/share/mysql/charsets/ > > 3) Out put show variables like '%coll%'; > > collation_connection utf8_general_ci > collation_database latin1_swedish_ci > collation_server latin1_swedish_ci > > Thanks for any help > > Regards > > Roberto Jobet > > > > > 6X velocizzare la tua navigazione a 56k? 6X Web Accelerator di Libero! > Scaricalo su INTERNET GRATIS 6X http://www.libero.it > > > > -- > MySQL General Mailing List > For list archives: http://lists.mysql.com/mysql > To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED] > > -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Import dump (4.0 > 4.1) and collation problem
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 difficult to setup. Anybody has already faced this problem ? Here's my current configuration: 1) my.cnf (only the mysqld section) [mysqld] user= mysql pid-file= /var/run/mysqld/mysqld.pid socket = /var/run/mysqld/mysqld.sock port= 3306 # Both location gets rotated by the cronjob. #log= /var/log/mysql.log log = /var/log/mysql/mysql.log basedir = /usr datadir = /db tmpdir = /tmp language= /usr/share/mysql/english 2) Output show variables like '%char%'; character_set_client utf8 character_set_connection utf8 character_set_database latin1 character_set_results utf8 character_set_server latin1 character_set_system utf8 character_sets_dir /usr/share/mysql/charsets/ 3) Out put show variables like '%coll%'; collation_connection utf8_general_ci collation_database latin1_swedish_ci collation_server latin1_swedish_ci Thanks for any help Regards Roberto Jobet 6X velocizzare la tua navigazione a 56k? 6X Web Accelerator di Libero! Scaricalo su INTERNET GRATIS 6X http://www.libero.it -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: collation problem
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 like client default characterset during a building the
mysql :)
Try commands :
select charset('_R');
select collation('_R');
select charset('price') from analit ;
select collation('price') from analit ;
If this command does not return koi8r then client gives to server
string withanother
charset as column 'price', but comparing two strings is possible only if
they have
identical charsets and collations .
Thats all
Andrey Kotrekhov wrote:
Добрый день.
Andrey Kotrekhov wrote:
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) NOT NULL default '',
`val` double NOT NULL default '0',
`city` char(16) NOT NULL default '',
`VIP` int(11) NOT NULL default '0',
`currency` char(8) NOT NULL default 'unit',
`label` int(11) NOT NULL default '0',
`status` int(11) NOT NULL default '0',
PRIMARY KEY (`d`,`service`,`price`,`type`,`city`,`VIP`),
KEY `city` (`city`),
KEY `d` (`d`),
KEY `label` (`label`)
) ENGINE=MyISAM DEFAULT CHARSET=koi8r
The request return me a error:
mysql> select * from analit where price rlike '_R';
ERROR 1267 (HY000): Illegal mix of collations
(koi8r_general_ci,IMPLICIT)
and (latin1_swedish_ci,COERCIBLE) for operation 'regexp'
I can't find this in docs.
I try to set LC_COLLATE in environtment variables
like
setenv LC_COLLATE ru_RU.KOI8-R
But there isn't any result.
What should I do?
Best regards.
___
Andrey Kotrekhov [EMAIL PROTECTED]
ISP Alkar Teleport
тел. +380 562 34-00-44
IMHO problem is when you try to check two differrent charsets, if
_R is
in a koi8r then you must try
select * from analit where price rlike _koi8r '_R';
Hmm... I have koi8 charset under FreeBSD,
and I have the same effect if I try to do:
select * from analit where price='something';
The problem take place if I try to compare char field without binary flag.
Any ideas.
Maybe something was changed in my.cnf from 4.1.1 to 4.1.2, was it?
Best regards.
___
Andrey Kotrekhov [EMAIL PROTECTED]
ISP Alkar Teleport
тел. +380 562 34-00-44
Best regards.
___
Andrey Kotrekhov [EMAIL PROTECTED]
ISP Alkar Teleport
тел. +380 562 34-00-44
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
collation problem
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) NOT NULL default '', `val` double NOT NULL default '0', `city` char(16) NOT NULL default '', `VIP` int(11) NOT NULL default '0', `currency` char(8) NOT NULL default 'unit', `label` int(11) NOT NULL default '0', `status` int(11) NOT NULL default '0', PRIMARY KEY (`d`,`service`,`price`,`type`,`city`,`VIP`), KEY `city` (`city`), KEY `d` (`d`), KEY `label` (`label`) ) ENGINE=MyISAM DEFAULT CHARSET=koi8r The request return me a error: mysql> select * from analit where price rlike '_R'; ERROR 1267 (HY000): Illegal mix of collations (koi8r_general_ci,IMPLICIT) and (latin1_swedish_ci,COERCIBLE) for operation 'regexp' I can't find this in docs. I try to set LC_COLLATE in environtment variables like setenv LC_COLLATE ru_RU.KOI8-R But there isn't any result. What should I do? Best regards. ___ Andrey Kotrekhov [EMAIL PROTECTED] ISP Alkar Teleport тел. +380 562 34-00-44 -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
