Performance: updateData with a filter + versioning can lead to many version records being created unecessarily

Description

The issue is that arbitrary arguments and filters on the updateData() call are not passed through to the versioning service that selects the existing records to do change control checking for.

This can lead to the versioning service believing that many more records are being updated than is the case if you have non-standard arguments that are used by interceptors to control what additional filters are added to the query (or not).

Environment

None

Assignee

Unassigned

Reporter

Dominic Watson

Labels

None

Accepted

Yes

Fix versions

Priority

Medium
Configure