#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
--------------------------------------------------------+-------------------
Comment (by Michael Radziej <[EMAIL PROTECTED]>):
There's an issue left when you use settings.DEFAULT_CHARSET: Mysql needs
to understand the character set name, right? But there are encodings that
have a name in mysql that is different from their name in python (e.g.,
'koi8r' vs. 'koi8-r'). Well, but it at least improves the situation.
The perfect solution would be:
* the django mysql backend cursor decodes query strings (execute,
executemany) from settings, when DEFAULT_CHARSET != 'utf8'
* mysqldb sets the charset for connections to utf8 and uses utf8 for
everything.
--
Ticket URL: <http://code.djangoproject.com/ticket/3754#comment:13>
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
-~----------~----~----~----~------~----~------~--~---
