Re: DATABASE_CHARSET setting, once and for all

2006-12-16 Thread Ivan Sagalaev
Jacob Kaplan-Moss wrote: > I remember looking at that patch and not being able to quite figure out what > it does... The main purpose of that patch was to be able to specify a charset for database independent of DEFAULT_CHARSET for two reasons: - database charset is different (and can't be cha

Re: DATABASE_CHARSET setting, once and for all

2006-12-15 Thread Jacob Kaplan-Moss
On 12/15/06 4:45 PM, Adrian Holovaty wrote: > Does anybody have comments on that patch before I commit it? I remember looking at that patch and not being able to quite figure out what it does... Let me see if I can figure it out: if I've got ``DATABASE_CHARSET = 'utf-8'`` and I pass a unicode

Re: DATABASE_CHARSET setting, once and for all

2006-12-15 Thread gabor
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 classe

DATABASE_CHARSET setting, once and for all

2006-12-15 Thread Adrian Holovaty
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 -- th