> Do you know which parts of django still use bytecode strings?

As far as I know, it's only newforms and this is why the topic was 
born: at the moment newforms work right until you want to put any non-
latin1 character through them to db. I've done the patch (#3370) which 
fixes the issue but it only works when your templates and your db are 
all in utf-8. And Ivan says this is wrong. From one hand I agree with 
him: this is not right. From other hand, I open the page http://
www.djangoproject.com/documentation/newforms/ and there's written: "We 
will REMOVE django.oldforms in the release ...". So if I start a new 
project based on django, or I extend existing project, there is very 
strong reason for me to use newforms, BUT they don't work. Confused ? 
Me too :(

Now I would like someone to explain me a few things before I start to 
do next patches :)
1. newforms are with unicode inside
2. ORM is with str inside
Should we (me, someone other) patch ORM to make it store everything in 
unicode inside it too, or at the moment unicode must be only inside 
newforms and newforms.model.save() must be fixed to put bytestring 
decoded data to models ?

And another thing I still don't understand is: let's pretend I use 
MySQL 4.0 with national charset and my templates are in the same 
charset too. How would work:
> the path: legacy (web) - unicode (newforms) - utf-8 (db connection) - legacy 
> (db)
specially the part "utf-8 (db connection)" ? In this situation we must 
convert strings to our app's encoding at the python side because our 
legacy db can't do it itself. But we use utf-8 for connection so who 
and where should do this conversion ?


--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to