#3754: mysql charset no longer defaults to utf-8
--------------------------------------------------------+-------------------
Reporter: Florian Apolloner <[EMAIL PROTECTED]> | Owner:
mtredinnick
Status: new | Component:
Database wrapper
Version: SVN | Resolution:
Keywords: | Stage:
Accepted
Has_patch: 1 | Needs_docs:
0
Needs_tests: 0 | Needs_better_patch:
0
--------------------------------------------------------+-------------------
Changes (by mtredinnick):
* owner: adrian => mtredinnick
Comment:
Either of these patches looks correct (thanks for the rapid response,
Andy) and I have a slighty preference for the latter. I'm not completely
sold on the idea of equating the database character set with
DEFAULT_CHARSET in the long-term. I think we do need a DATABASE_CHARSET
parameter, but that is definitely post-0.96 work. For now, restoring the
previous default behaviour as the default is a nice solution for existing
users, so we'll go with that. I'll apply this in a few hours, once I've
had a chance to test things.
--
Ticket URL: <http://code.djangoproject.com/ticket/3754#comment:12>
Django Code <http://code.djangoproject.com/>
The web framework for perfectionists with deadlines
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en
-~----------~----~----~----~------~----~------~--~---
