I’m wondering if this is expected behaviour, on the commit of an edit screen where I am also bringing in Audit Log entities to display, there are a large number of EntityLogAttr entities in the modifiedInstances part of the dataContext. Why would this be? They aren’t being modified and I’m concerned there may be a performance impact. See screenshot below as well for info.
Hi,
These entities are not persistent and they shouldn’t bring a performance impact.
They are automatically populated for any EntityLogItem by the io.jmix.audit.impl.EntityLogItemDetachListener .
As you can find out from the source code of this class, you can exclude “changes” field from the fetch plan for the EntityLogItem, then attributes won’t be populated.
