#16251: Db/Models: distinction btw "null" and "blank"
-----------------------------------------+-------------------------------
Reporter: MixedContent | Owner: nobody
Type: Uncategorized | Status: closed
Milestone: | Component: Documentation
Version: 1.3 | Severity: Normal
Resolution: invalid | Keywords:
Triage Stage: Unreviewed | Has patch: 0
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 | Easy pickings: 0
UI/UX: 0 |
-----------------------------------------+-------------------------------
Changes (by aaugustin):
* status: new => closed
* resolution: => invalid
Comment:
The document you're referring to is just a summary:
> [The options are] fully explained in the
[[https://docs.djangoproject.com/en/1.3/ref/models/fields/#common-model-
field-options|reference]], but here's a quick summary of the most often-
used ones
[[BR]]
Your question is actually about the behavior of `null`, and the detailed
answer is in the reference:
https://docs.djangoproject.com/en/1.3/ref/models/fields/#null
If this explanation is still not sufficiently clear, could you reopen the
ticket?
--
Ticket URL: <https://code.djangoproject.com/ticket/16251#comment:2>
Django <https://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.
