Are u sure it is the way to do ? In the Upgrading.mysql help file, they say that the default charset should not be utf-8. In my database, all my tables are set as utf-8 but the default charset of the database is latin1.
Gian Luca Gobbi wrote: > > Hi, > you must add/change this lines in your my.cnf: > > [client] > default-character-set = utf8 > > [mysqld] > default-character-set=utf8 > character_set_server=utf8 > collation_server=utf8_general_ci > init_connect='SET collation_connection = utf8_general_ci' > init_connect='SET CHARACTER_SET utf8' > init_connect='SET NAMES utf8' > > [mysql] > default-character-set=utf8 > > Stop/start you mysqld and you have: > > mysql> show variables like 'c%'; > +--------------------------+----------------------------+ > | Variable_name | Value | > +--------------------------+----------------------------+ > | character_set_client | utf8 | > | character_set_connection | utf8 | > | character_set_database | utf8 | > | character_set_filesystem | binary | > | character_set_results | utf8 | > | character_set_server | utf8 | > | character_set_system | utf8 | > | character_sets_dir | /usr/share/mysql/charsets/ | > | collation_connection | utf8_general_ci | > | collation_database | utf8_general_ci | > | collation_server | utf8_general_ci | > | completion_type | 0 | > | concurrent_insert | 1 | > | connect_timeout | 10 | > +--------------------------+----------------------------+ > 14 rows in set (0.00 sec) > > > After these modifications all works well. > > -- > Gian Luca Gobbi > > > > ________________________________ > > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of BALINT > Bekeny > Sent: Wednesday, September 03, 2008 11:07 AM > To: [email protected] > Subject: Re: [rt-users] Charset issues after upgrade to 3.8.1 > > > Hi, > > I reported the same problem here (but nobody answered): > http://lists.bestpractical.com/pipermail/rt-users/2008-August/053512.html > > I think there is a lack in the mysql upgrade document or in the upgrade > script. > I did it on a test environment and didn't have time to find out the real > solution, > so I delayed the migration of the real system. > > Some more information: > - After migration, new entries (for example CF-s) seemed good, even if > they have non-ascii characters. > - In mysql CLI: show variables like 'c%' shows that everything is utf8 > (so this seems good) > > Any suggestion? > > Thanks, > -- > Bekény > > > > On Tue, Sep 2, 2008 at 5:28 PM, Emmanuel Lacour <[EMAIL PROTECTED]> > wrote: > > > On Tue, Sep 02, 2008 at 08:14:55AM -0700, F350 wrote: > > > > Thanks a lot for your help and time Emmanuel. > > I updated all the tickets, CF and templates that look corrupted. > > Next time i'll make sure I do the updates on a test server :) > > > > > You're welcome :) > > Using a test server or a test db/rt instance is a must have ;) > > _______________________________________________ > > > > _______________________________________________ > http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users > > Community help: http://wiki.bestpractical.com > Commercial support: [EMAIL PROTECTED] > > > Discover RT's hidden secrets with RT Essentials from O'Reilly Media. > Buy a copy at http://rtbook.bestpractical.com > > -- View this message in context: http://www.nabble.com/Charset-issues-after-upgrade-to-3.8.1-tp19267620p19308775.html Sent from the Request Tracker - User mailing list archive at Nabble.com. _______________________________________________ http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users Community help: http://wiki.bestpractical.com Commercial support: [EMAIL PROTECTED] Discover RT's hidden secrets with RT Essentials from O'Reilly Media. Buy a copy at http://rtbook.bestpractical.com
