#952: [patch] Allow for database client encoding configuration from project
settings
---------------------------+------------------------------------------------
Reporter: [EMAIL PROTECTED] | Owner: adrian
Status: reopened | Component: Database wrapper
Version: SVN | Resolution:
Keywords: | Stage: Design decision needed
Has_patch: 1 | Needs_docs: 0
Needs_tests: 0 | Needs_better_patch: 1
---------------------------+------------------------------------------------
Changes (by Michael Radziej <[EMAIL PROTECTED]>):
* stage: Accepted => 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/952#comment:56>
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
-~----------~----~----~----~------~----~------~--~---
