#26918: Documentation Clarification on pre_save signal updated_fields
-------------------------------------+-------------------------------------
Reporter: stantond | Owner: nobody
Type: | Status: closed
Cleanup/optimization |
Component: Database layer | Version: 1.9
(models, ORM) |
Severity: Normal | Resolution: needsinfo
Keywords: | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 1 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by charettes):
* status: new => closed
* needs_better_patch: => 0
* resolution: => needsinfo
* needs_tests: => 0
* needs_docs: => 0
Comment:
> Will updated_fields be populated if the object is being created, or only
when updated?
We already document that
[https://docs.djangoproject.com/en/1.9/ref/models/instances/#forcing-an-
insert-or-update using update_fields will force the object to be updated]
> What would updated_fields content look like/format/layout?
The linked documentation makes it clear to me that `update_fields` is a
`set()`.
Can you formulate a documentation adjustment in the form of a patch or an
annotated text? I'm not sure about what you are suggesting here.
--
Ticket URL: <https://code.djangoproject.com/ticket/26918#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/066.dc8d486d51d3c862eaaf22d25669e255%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
