#35659: Document db_default behaviour before instances are saved
-------------------------------------+-------------------------------------
Reporter: Markus Andresen | Owner: rajat0806
Type: | Status: assigned
Cleanup/optimization |
Component: Documentation | Version: 5.0
Severity: Normal | Resolution:
Keywords: db_default | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 1
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by rajat0806):
I checked the current main branch and noticed that the db_default
documentation already mentions that a DatabaseDefault object is returned
on unsaved model instances when Field.default is not set.
Is there still remaining work expected on this ticket, such as adding a
small example showing when to use Field.default together with db_default?
--
Ticket URL: <https://code.djangoproject.com/ticket/35659#comment:12>
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 view this discussion visit
https://groups.google.com/d/msgid/django-updates/0107019eb8478cd1-4346475c-7676-47a0-acc4-423914224034-000000%40eu-central-1.amazonses.com.
