thanks too for this.
rather than alter the table manually of course, it should have been created correctly the first time. mysql will create new tables with the character encoding of the database. you can set that this way: alter database cruxxial_md CHARACTER SET = utf8; now tables created with syncdb will have the correct encoding. mysql will create new DATABASES with the charset that was used to start the server mysqld --character-set-server=utf8; which is often out of our control on hosted environments, or even when using handy os x control panels to start the db. so I guess a tip is : when you create the database, make sure to alter the charset before running syncdb. but what does the unittest runner do ?? (since it creates its own database) it also creates a latin1 db: CREATE TABLE `website_releasefeedback` ( ... ) ENGINE=MyISAM DEFAULT CHARSET=latin1 I wonder if django should create all tables with UTF-8 regardless of how the db is configured. On Oct 6, 11:14 am, tamonash <[EMAIL PROTECTED]> wrote: > Thanks Malcolm, > You solved my problem. These tables were something that I was using > from a previous application so all the mess.. > > mysql> alter table ac_project_messages modify title varchar(100) > character setutf8default NULL; > Query OK, 81 rows affected (0.20 sec) > Records: 81 Duplicates: 0 Warnings: 0 > > mysql> alter table ac_project_messages modify text text character setutf8; > Query OK, 81 rows affected (0.05 sec) > Records: 81 Duplicates: 0 Warnings: 0 > > And WOW!! it worked. Thanks again.. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com 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 -~----------~----~----~----~------~----~------~--~---
