Ivan Sagalaev: > Michael Radziej wrote: >> Ivan Sagalaev: >> >>> 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. >> I'm not sure if the fix is on the right level. StrAndUnicode is used >> in a lot of places. Is it sure that it won't put xmlcharref-encoded >> data into the database? I only had a very quick look on it (and I >> need to go to a meeting now). > > Uhm... Are we talking about the same patch? This is it: > http://code.djangoproject.com/attachment/ticket/3370/models.py.diff > > It doesn't mention StrAndUnicode at all.
(meeting postponed ...) 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. Michael -- noris network AG - Deutschherrnstraße 15-19 - D-90429 Nürnberg - Tel +49-911-9352-0 - Fax +49-911-9352-100 http://www.noris.de - The IT-Outsourcing Company --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
