/
Change log sometimes showing non-existing changes [5.2.2-B2]

Change log sometimes showing non-existing changes [5.2.2-B2]

Owned by Alex
Last updated: Aug 13, 2020

In the  INP-1116 - Getting issue details... STATUS  task an improvement was made to support calling "kDBItem::Update" with a limited set of fields. The use case would be restricting fields in the "UPDATE" SQL statement to avoid accidental overwrite of fields, that weren't changed right now, but were changed in parallel by another user.

When "Change Log" functionality is used, then changes not written into the database would also be written into the logs.

Solution

  1. improve these methods to allow specifying field limitation given to "kDBItme::Update" call:
    1. \kDBItem::setModifiedFlag
    2. \kDBItem::LogChanges
  2. in the "\kDBItem::LogChanges" method reduce list of changes to fields given in limitation

Related Tasks

INP-1789 - Getting issue details... STATUS