Michael Radziej wrote: > (meeting postponed ...) Nice :-)
> You're right, sorry. I was in a different ticket and somehow thought > it was the same. > > Yes, #3370 looks interesting and is a different solution. I'm not > sure whether it deals with all the issues of this thread. I tried to show that it leaves out only two things: - if DEFAULT_CHARSET is different than DB charset it won't work (but it's a weird situation, most legacy systems have one legacy encoding for both) - it doesn't help if unicode is actually put into models or in raw SQL manually but this bug was never about it anyway and won't break anything since it fixes newforms, not backends --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" 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-developers?hl=en -~----------~----~----~----~------~----~------~--~---
