On Mon, May 28, 2007 at 04:26:17PM -0500, Jeremy Dunck wrote: > > 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.
Do we need such a settings or we really need to *copy* database encoding so that tests are done exactly as the application database. (if it's possible to use other than utf8...). That would prevent people from runnnig wanderfull tests on a well configured db when the real db is still "SQL_ASCII" just becouse template1 was shipped that way! sandro *:-) --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
