>What are your thoughts on the modified proposal stated in my reply to >Luke (i.e., keep both, but have blank automatically set to True when >null=True and then allow the explicit setting of blank=False)?
blank=True with implicit null=True isn't probably what users would expect when applying it to charfields. And having a rule where charfields have null=False in combination with blank=True and non-charfields have null=True with blank=True is rather icky - context-sensitive defaults are bound to irritate. I myself have blank=True quite often with charfields, much more often than with non-charfields, so I think I am still -1 on that one. bye, Georg --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
