On 2/20/06, hugo <[EMAIL PROTECTED]> wrote: > > 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.
I never intended it to apply to charfields, but I see your and Luke's point regarding the context-sensitive defaults; it still feels like a non-optimal situation to me, but perhaps one without an optimal solution at the moment. Oh well, proposal withdrawn. :-) --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
