Well... I just restored my database from production dump... On prod I have correct UTF-8
On Wed, May 20, 2009 at 4:49 PM, Karen Tracey <[email protected]> wrote: > On Wed, May 20, 2009 at 9:37 AM, Oleg Oltar <[email protected]> wrote: > >> Hm... You're right...But I don't understand how it happened... I used sync >> db to create those table >> > > syncdb doesn't specify a character set, it uses the database default. I > don't understand how some of your tables would have one value while others > have a different one unless you created them at different times while the > server was set to have different defaults. > > >> >> mysql> show create table articleManager_categoty\G >> *************************** 1. row *************************** >> Table: articleManager_categoty >> Create Table: CREATE TABLE `articleManager_categoty` ( >> `id` int(11) NOT NULL AUTO_INCREMENT, >> `categoty` varchar(200) NOT NULL, >> `name` varchar(200) NOT NULL, >> PRIMARY KEY (`id`) >> ) ENGINE=MyISAM AUTO_INCREMENT=4 DEFAULT CHARSET=latin1 >> 1 row in set (0.00 sec) >> >> mysql> >> >> >> can you suggest a command to change charset? >> > > That's the doc I pointed to. It's something like 'ALTER TABLE > articleManager_categoty CONVERT TO CHARACTER SET UTF8' but I'm not 100% sure > without trying it that that is the correct syntax. > > Karen > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
