Adrian Holovaty wrote: > I recently implemented the form_for_model() helper function in > django.newforms, which returns a Form class for a given Model class. > It has a create() method, which actually creates the object from form > data. This is the replacement for automatic AddManipulator classes. > > But there's a problem -- the newforms library returns all data in > Unicode, whereas the PostgreSQL psycopg1 database backend only accepts > bytestrings and does not automatically convert Unicode to bytestrings > (see http://code.djangoproject.com/ticket/3115 ). As a somewhat > related issue, the ticket http://code.djangoproject.com/ticket/952 > proposes a DATABASE_CLIENT_CHARSET setting. This would specify the > charset used by your database. Currently Django assumes MySQL uses > utf-8 in the database, and (if I remember correctly) assumes other > databases are using the encoding specified by DEFAULT_CHARSET. > > Does anybody have comments on that patch before I commit it? >
+1 gabor --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
