On Mon, 2007-05-28 at 16:26 -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. > > FWIW, as a workaround, in Mysql's my.cnf, you can set: > character_set_database = 'utf8'
Yeah, I'm aware of this. It's only a workaround, as you say, though, since it makes tests dependent on configuration outside of Django. There are already some implicit assumptions like that in the tests (if you database can't hold characters that are also in the latin1 charater set, encoded suitably to the encoding of your database, tests will fail mysteriously). But don't tell anybody that. We'll keep as just our little secret. :-) > 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). Agreed. Since both servers allow you to specify the encoding at creation time, I'll add support for TEST_DATABASE_CHARSET and TEST_DATABASE_COLLATION settings today (to trunk, since this isn't Unicode specific). That should make things more portable. Regards, Malcolm --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
