#3328: null=True should imply blank=True
------------------------+---------------------------------------------------
Reporter: SmileyChris | Owner: adrian
Status: new | Component: Database wrapper
Version: SVN | Keywords:
Stage: Unreviewed | Has_patch: 1
------------------------+---------------------------------------------------
For models, I can't ever think of a case when you would want `null=True`
and '''not''' want `blank=True`. If there is, it's definitely rare, so
having to enter both for the normal case seems redundant.
Currently, for model fields, `blank` always defaults to `False`.
This proposal is that `blank` is set to whatever `null` is set to unless
explicitly given.
--
Ticket URL: <http://code.djangoproject.com/ticket/3328>
Django Code <http://code.djangoproject.com/>
The web framework for perfectionists with deadlines
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Django
updates" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en
-~----------~----~----~----~------~----~------~--~---
