#952: [patch] Allow for database client encoding configuration from project
settings
---------------------------+------------------------------------------------
Reporter: [EMAIL PROTECTED] | Owner: adrian
Status: closed | Component: Database wrapper
Version: SVN | Resolution: wontfix
Keywords: | Stage: Design decision needed
Has_patch: 1 | Needs_docs: 0
Needs_tests: 0 | Needs_better_patch: 1
---------------------------+------------------------------------------------
Changes (by mtredinnick):
* status: reopened => closed
* resolution: => wontfix
Comment:
In light of the changes in the unicode branch, this setting is no longer
needed. All our supported database backends that can handle variable
server encodings take care of that information transparently. We just hand
them unicode strings or UTF-8 bytestrings and it should work
transparently.
So this is wontfix and the root problem will go away once unicode branch
merges into trunk.
--
Ticket URL: <http://code.djangoproject.com/ticket/952#comment:61>
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
-~----------~----~----~----~------~----~------~--~---
