gabor wrote: > 3. will assume the database is in DEFAULT_CHARSET > - maybe can we somehow ask the db for it's charset? > > so, what do you think? > or should we make it possible to have a system with mixed charsets? > (well, maybe having a different DB_CHARSET and a DEFAULT_CHARSET could > work. maybe)
Yes, this is very desirable for systems that use legacy DB but want to output good modern utf-8 for users. There is a ticket implementing this setting (http://code.djangoproject.com/ticket/952) but now I see that Jacob has marked it WONTFIX. And even after reading an explanation I don't get the reason... This still looks like a requirement for unicodification rather than something that will be superseded. Jacob, could you elaborate on this? --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
