Implement support for only posting back the changed fields when saving an entity. This will reduce network overhead and will also give some advantages like reverting unintended field changes.
can be done by instantiating a dict of reference fields in Entity __init__(), and comparing on save().
This will also simplify the _migration_asst() functions in Campaign and Strategy written for the spend cap and pacing migrations, which do this in a limited scope.
FodT
commented
7 years ago
Implement support for only posting back the changed fields when saving an entity. This will reduce network overhead and will also give some advantages like reverting unintended field changes.
can be done by instantiating a dict of reference fields in Entity
__init__(), and comparing onsave().This will also simplify the
_migration_asst()functions inCampaignandStrategywritten for the spend cap and pacing migrations, which do this in a limited scope.