On 16-May-08, at 5:48 PM, Andre Meyer wrote:
> still need to figure out why ;-) by default, django treats all fields as not null and not blank. Usually, the 'null' part is enforced at the database level and the 'blank' part at django level. So for fields like CharFields, saying null is allowed is not the same as saying blank is allowed. -- regards kg http://lawgon.livejournal.com http://nrcfosshelpline.in/code/ --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@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-users?hl=en -~----------~----~----~----~------~----~------~--~---