#952: [patch] Allow for database client encoding configuration from project
settings
------------------------------+---------------------------------------------
Reporter: [EMAIL PROTECTED] | Owner: adrian
Type: defect | Status: closed
Priority: normal | Milestone: normal
Component: Database wrapper | Version: SVN
Severity: normal | Resolution: wontfix
Keywords: |
------------------------------+---------------------------------------------
Changes (by jacob):
* resolution: => wontfix
* status: new => closed
Comment:
This is a tricky one.
Whatever we choose is going to change when we deal with the whole sticky
unicodification aspect... so for now, I'm going to punt and mark this
WONTFIX with the understanding that we'll fix it in a comprehensive manner
in the future. For the record, the answer now is to just make sure your
database's default encoding *does* match, which hopefully isn't too much
of a nasty hack.
--
Ticket URL: <http://code.djangoproject.com/ticket/952>
Django <http://code.djangoproject.org/>
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
-~----------~----~----~----~------~----~------~--~---
