#26918 closed Cleanup/optimization (fixed)
Documentation Clarification on pre_save signal updated_fields
| Reported by: | Daniel Stanton | Owned by: | nobody |
|---|---|---|---|
| Component: | Database layer (models, ORM) | Version: | 1.9 |
| Severity: | Normal | Keywords: | |
| Cc: | Triage Stage: | Unreviewed | |
| Has patch: | no | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | yes | UI/UX: | no |
Description
Will updated_fields be populated if the object is being created, or only when updated?
What would updated_fields content look like/format/layout?
https://docs.djangoproject.com/en/1.9/ref/signals/#pre-save
For all supported versions.
Change History (6)
comment:1 by , 8 years ago
| Resolution: | → needsinfo |
|---|---|
| Status: | new → closed |
comment:3 by , 8 years ago
@stantond, please confirm the patch suggested by Tim is along the clarification you had in mind.
Note:
See TracTickets
for help on using tickets.
We already document that using update_fields will force the object to be updated
The linked documentation makes it clear to me that
update_fieldsis aset().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.