On 06.01-07:38, Lee Braiden wrote: [ ... ] > On Tue, 2009-01-06 at 00:05 -0700, Jeff Anderson wrote: > > Malcolm Tredinnick wrote: > > > I don't think we'd want to get too subtle here. Either it makes > > > sense for all non-text fields, or it doesn't. > > Agreed I simply haven't spent any time thinking about this particular > > problem in respect to any field other than an IntegerField. I can't > > think of any non-text field that it may not make sense with.
i would be against unifying the options as i can imagine a more complex environment (i.e. a database trigger or complex type not known to django) where there may be a distinction and i believe the current distinction is a clear one. it may be worthwile to imply that setting 'null=True' also sets 'blank=True' unless explictly overridden with 'blank=False'. however, the converse implication is faulty (i.e. 'blank=True' != 'null=True') because 'blank' relates to the admin interface, whereas 'null' refers to the data model. it is correct to imply the interface and formatting from the data model but not to imply the data contraints from the interface. IMHO. --~--~---------~--~----~------------~-------~--~----~ 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 django-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
