#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 Andreas Bergström):
There is the django-dirtyfields that will at least tell you if a model is
dirty and what fields that's dirty, but it won't do the saving...
https://github.com/romgar/django-dirtyfields
--
Ticket URL: <https://code.djangoproject.com/ticket/27017#comment:5>
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 django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/068.cd446c4cac6854a749f3704bc1d8ff81%40djangoproject.com.
