I'd like to take your attention on a side effect of missing FloatField.formfield(): CharField is used in newforms that means that null=True, blank=True will use an empty strings that correctly makes PostgreSql quite angry... (sqlite doesn't bother...)
Digging into the open tickets I see the reason is that there is a "design decision" to be taken wheather to use decimals or floats (how can a FloatField be mapped into a decimal.decimal...). Ticket 2365 shows the issue: http://code.djangoproject.com/ticket/2365 If we really want to push newform I see that these kind of problems must be solved pretty soon. back in a while with new issues... sandro *:-) PS: i really appreciate the work that is being done and working with django is a real pleasure... ;-) --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to [email protected] 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 -~----------~----~----~----~------~----~------~--~---
