#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 Ivan Sagalaev <[EMAIL PROTECTED]>):
* cc: [EMAIL PROTECTED] (added)
Comment:
Jacon, this ticket was mentioned in a thread on django-developers but I
suppose those messages are easy to miss so I repost the relevant bits
here.
The ongoing unicodification will actually require support for legacy
encoded DBs and this ticket looks like a best place to do this. So may be
instead of wontfixing it it's better to rework patches for the new vision
(which means just dropping encoding into DEFAULT_CHARSET leaving data from
DB in unicode)?
--
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
-~----------~----~----~----~------~----~------~--~---
