#3754: mysql charset no longer defaults to utf-8
--------------------------------------------------------+-------------------
Reporter: Florian Apolloner <[EMAIL PROTECTED]> | Owner:
adrian
Status: new | Component:
Database wrapper
Version: SVN | Resolution:
Keywords: | Stage:
Accepted
Has_patch: 1 | Needs_docs:
0
Needs_tests: 0 | Needs_better_patch:
1
--------------------------------------------------------+-------------------
Comment (by Michael Radziej <[EMAIL PROTECTED]>):
Just for the record: Using DEFAULT_CHARSET instead of 'utf8' fixes #952;
Either 'utf8' or DEFAULT_SETTINGS should fix #1356 and #3370 (but this
needs testing).
The old mysql backend did not allow this solution. The problems have been
discussed--ad nauseum--in [http://groups.google.com/group/django-
developers/browse_thread/thread/4b71be8257d42faf this thread on django-
developers].
I'm going to post a request to test this patch to django-developers.
--
Ticket URL: <http://code.djangoproject.com/ticket/3754#comment:10>
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
-~----------~----~----~----~------~----~------~--~---
