On 6/19/08, Russell Keith-Magee <[EMAIL PROTECTED]> wrote: > The only obvious thing I can glean from your stack traces is a > possible language problem - the last stack trace is complaining of a > collation mix, which suggests that your MySQL install isn't using utf8 > all the time.
Yes, it is the intention. If Django requires test database with charset UTF8, IMHO it should create it using related clause. as well as proper engine should be choosen if we care about reference integrity, e.g. SET storage_engine=InnoDB; CREATE DATABASE xxx DEFAULT CHARACTER SET utf8 COLLATE utf8_xxx_ci; Should I create a ticket ;-) Peter --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
