Thanks a lot for all these infos,
now I haven't time to look on mailing lists :
I've got to modify all my Databases to be able to show correct accentuated
datas on all my websites :(
bye
Christian Hammers a écrit :
tags 385960 + upstream moreinfo
stop
Hi
On 2006-09-04 [EMAIL PROTECTED] wrote:
I always used iso-8859-15 as charset for all my databases, but it seems that
the upgrade modified something in the parameters to use utf-8 instead. I
would like to know how I could get back the previous behaviour. For the
moment all my databases are unusable
As far as I know that have been no changes to the locales. Can you show
SHOW CREATE DATABASE xxx;
SHOW CREATE DATABASE parnasse
=>
CREATE DATABASE `parnasse` /*!40100 DEFAULT CHARACTER SET latin1 COLLATE
latin1_general_ci */
SHOW CREATE TABLE xxx.yyy;
SHOW CREATE TABLE CLIENTS
=>
CREATE TABLE `CLIENTS` (\n `ID_CLIENT` int(11) NOT NULL auto_increment,\n `TITRE` varchar(10) character set latin1
default NULL,\n `TITRE2` varchar(255) character set latin1 default NULL,\n `NOM` varchar(100) character set latin1 NOT
NULL default '',\n `PRENOM` varchar(100) character set latin1 NOT NULL default '',\n `ADRESSE` varchar(100) character
set latin1 default NULL,\n `CODE_POSTAL` varchar(5) character set latin1 default NULL,\n `VILLE` varchar(100)
character set latin1 default NULL,\n `TELEPHONE` varchar(25) character set latin1 default NULL,\n `E_MAIL`
varchar(100) character set latin1 default NULL,\n `ZONE_GEOGRAPHIQUE` smallint(6) default NULL,\n `DATE_SAISIE`
datetime NOT NULL default '0000-00-00 00:00:00',\n `DATE_DE_NAISSANCE` date default NULL,\n `OBSERVATIONS`
varchar(255) character set latin1 default NULL,\n `SEXE` char(1) character set latin1 NOT NULL default '',\n `TARIF`
smallint(6) NOT NULL default '0',\n `LOGIN` varchar(20) character set latin1 default NULL,\n `PASSWORD` varchar(20)
character set latin1 default NULL,\n `VALIDATION` tinyint(1) default '0',\n PRIMARY KEY (`ID_CLIENT`)\n)
ENGINE=MyISAM AUTO_INCREMENT=1212 DEFAULT CHARSET=latin1 COLLATE=latin1_general_ci
Hm, I'm wondering why both statements say "CHARSET=latin1". Did you just
wrote UTF8 in it without changing the table charset?
SHOW VARIABLES LIKE "char%";
in phpmyadmin opened with "French (iso-8859-15)"
=>
character_set_client utf8
character_set_connection latin1
character_set_database latin1
character_set_filesystem binary
character_set_results utf8
character_set_server latin1
character_set_system utf8
character_sets_dir /usr/share/mysql/charsets/
logged in mysql
=>
+--------------------------+----------------------------+
| Variable_name | Value |
+--------------------------+----------------------------+
| character_set_client | latin1 |
| character_set_connection | latin1 |
| character_set_database | latin1 |
| character_set_filesystem | binary |
| character_set_results | latin1 |
| character_set_server | latin1 |
| character_set_system | utf8 |
| character_sets_dir | /usr/share/mysql/charsets/ |
+--------------------------+----------------------------+
I've never really used a different charset but I would assume that
there's too much "latin1" in the above table :(
As I didn't find Manual -> History on dev.mysql.com, I looked into
changelogs, but I didn't see any mention of such change in the changelog.
I meant this here: http://dev.mysql.com/doc/refman/5.0/en/news.html but
cannot find something with charset either.
I don't know how to help you here so I suggest asking on the mysql mailing
list. Send them the same create table infos and maybe do a mysqldump of
your tables to verify that the data in them really still is UTF8 and has
not accidently converted into ISO by one of your apps.
bye,
-christian-
