Well I've got success after applying a patch to django's code. Actually there are 2 patches against django/db/backends/mysql/base.py: 1. it forces to run SET NAMES 'utf8' after connection. This is wrong, and I replaced it with SET NAMES 'cp1251'. Ofcourse, it should be a setting in settings.py but let's leave it until we find a complete solution. This patch is enough to work without problems with oldforms and site running in 'windows-1251' and database running in 'cp1251' 2. In DatabaseWrapper class, method cursor, one more value to kwargs: 'charset': 'cp1251'
These 2 patches allowed me to use newforms too (remember that clean_data is in unicode by design) I am sure everything works ok when unicode is used everywhere (database, site, templates etc) but what about using django in national non-unicode environments ? Why dont' just add a setting DATABASE_CHARSET with default value 'utf8' that can be changed in user's settings.py ? I've sent the patch for it some time ago (http://code.djangoproject.com/ticket/1528) but it was rejected because there was better patch http://code.djangoproject.com/ticket/952 BUT there is no such code in the current svn version. Dunno why. But for me it seems to be required --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@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-users?hl=en -~----------~----~----~----~------~----~------~--~---
