Michael Radziej wrote: > A few days ago, I wrote: >> I see three ways to fix the problem in #3370: >> >> a) newforms stops passing unicode strings to the Database API and uses >> bytestrings. >> >> b) the database wrapper in Django sets connection.charset (but needs to >> translate the charset name since the databases don't understand all >> charset name variants, see ticket #952 here). This is the approach of >> the patches in tickets #1356 and #3370. >> >> c) the database wrapper in Djago must check whether it gets unicode. In >> this case, it needs to encode it into a bytestring. > > I now see a fourth way that would resolve #952 at the same time: > > d) make the database wrapper accept both unicode and bytestrings in > the models, but always pass unicode strings to the database backend.
Michael, the ticket http://code.djangoproject.com/ticket/3370 just got a patch that does a) and it's really small. It's not as full as having b) and d) but I think they are really a corner cases: b) for different encodings in DB and in web, d) for handling unicode input to DB backend *without* newforms. In other words I think that patch is just right for current situation because it fixes the bug for people trying to use newforms now. I'm +1 on just committing it as is. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
