Jacob Kaplan-Moss wrote:
> I remember looking at that patch and not being able to quite figure out what
> it does...
The main purpose of that patch was to be able to specify a charset for
database independent of DEFAULT_CHARSET for two reasons:
- database charset is different (and can't be changed for some reason)
- databases use different encoding names that are backend specific
("unicode", "utf8", "utf-8" etc.)
For the latter part there are charset mappings for MySQL and Postgres
which can be further extended later.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send email to django-developers@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-developers?hl=en
-~----------~----~----~----~------~----~------~--~---
