Changes between Initial Version and Version 1 of Ticket #36108, comment 1


Ignore:
Timestamp:
Jan 17, 2025, 1:13:19 PM (11 hours ago)
Author:
Simon Charette

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #36108, comment 1

    initial v1  
    99In other words Django doesn't keep track of model instance fields that were assigned a different value since their last retrieval / persistence to the database and will [https://docs.djangoproject.com/en/5.1/ref/models/instances/#specifying-which-fields-to-save default to saving all fields] if `update_fields` is not specified which is denoted by `update_fields=None` in signal receivers.
    1010
    11 If you want to keep track of which field changed and [https://django-model-utils.readthedocs.io/en/latest/utilities.html#field-tracker you should use a third party application for that].
     11If you want to keep track of which field changed you should write your own tracker of old-field values and flush it on `save()` or [https://django-model-utils.readthedocs.io/en/latest/utilities.html#field-tracker use a third party application that does it for you].
Back to Top