On Sunday 19 February 2006 00:21, Tom Tobin wrote: > Hmm; while it would be good to support edge cases like that, I think > the default should make general-use cases easier. Maybe null=True > should automatically set blank=True for non-string fields, but still > allow one to then explicitly set blank=False?
Like George, I'm -1 on this kind of special-casing, and the default value behaviour would be confusing. I can only imagine the API docs will be longer and more complicated with this change, and would require you to remember more. Luke -- "My middle name is 'Organised'! My first name is 'Poorly'." Luke Plant || L.Plant.98 (at) cantab.net || http://lukeplant.me.uk/ --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
