#30401: Clarification about when a default value is assigned to a ModelField
-------------------------------------+-------------------------------------
Reporter: Vinicius Assef | Owner: nobody
Type: | Status: closed
Cleanup/optimization |
Component: Documentation | Version: master
Severity: Normal | Resolution: wontfix
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 felixxm):
* status: new => closed
* version: 2.2 => master
* resolution: => wontfix
Comment:
Thanks for the report, however it is not confusing IMO. Moreover an extra
clarification is in the same paragraph
> "The default value is used when **new model instances are created** and
a value isn't provided for the field. When the field is a primary key, the
default is also used when the field is set to None."
We try to avoid wording changes unless it's a big problem as it creates
extra work for documentation translators.
--
Ticket URL: <https://code.djangoproject.com/ticket/30401#comment:1>
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 unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/069.df3db397d0cef0689fe8b025fe23a23c%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
