#1356: [patch] database charset and mysql backend
----------------------------------+-----------------------------------------
Reporter: little | Owner: adrian
Status: new | Component: Database wrapper
Version: | Resolution:
Keywords: mysql charset utf8 | Stage: Design decision
needed
Has_patch: 1 | Needs_docs: 0
Needs_tests: 1 | Needs_better_patch: 1
----------------------------------+-----------------------------------------
Changes (by Michael Radziej <[EMAIL PROTECTED]>):
* needs_better_patch: 0 => 1
* needs_tests: 0 => 1
* stage: Ready for checkin => Design decision needed
Comment:
We have a bit of chaos here ... Tickets #3370, #1356 and probably #952 all
are about this problem, all are accepted, and #3370 and #1356 have very
similar patches. I ask everybody to continue discussion in django-
developers ("unicode issues in multiple tickets"), and I ask the authors
of these three tickets to work together to find out how to proceed.
As long as it's not clear which path to take, I mark all bugs as "design
decision needed." (I assume that the other reviews were not aware of the
competing tickets.)
http://groups.google.com/group/django-
developers/browse_thread/thread/4b71be8257d42faf
--
Ticket URL: <http://code.djangoproject.com/ticket/1356#comment:7>
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
-~----------~----~----~----~------~----~------~--~---
