#27017: Why doesn't Django's Model.save() save only the dirty fields by default?
And how can I do that if I want?
-------------------------------------+-------------------------------------
Reporter: prajnamort | Owner: nobody
Type: Uncategorized | Status: closed
Component: Database layer | Version: 1.8
(models, ORM) |
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
-------------------------------------+-------------------------------------
Comment (by Jack Linke):
Just a note for anyone coming across Andreas' comment above. django-
dirtyfields does now make it possible to update only the dirty (changed)
fields: https://django-dirtyfields.readthedocs.io/en/develop/#saving-
dirty-fields
--
Ticket URL: <https://code.djangoproject.com/ticket/27017#comment:6>
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 on the web visit
https://groups.google.com/d/msgid/django-updates/068.83b4cdb98237dce303f61868bd0727ee%40djangoproject.com.
