On 5/28/07, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote: > Okay... time to fix that problem then. Probably need to introduce a > settings for tests only for database encoding. I should have done that > when I first saw the problem instead of trying to dodge around it.
FWIW, as a workaround, in Mysql's my.cnf, you can set: character_set_database = 'utf8' In postgres, new databases are created from the template1 system database; new databases will have whatever encoding that database has. (template0 is the pristine DB shipped with postgres and should never be changed, but you should feel free to change template1 as is useful). --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
