AnsweredAssumed Answered

setFormKey causes extra query

Question asked by ptrepagnier on Oct 31, 2014
Latest reply on Nov 3, 2014 by jbarrez
If you create a task query, it looks like Activiti actually executes N+1 queries due to setFormKey in TaskEntity.  All of the other properties in TaskEntity have versions that do not cascade (e.g. setTaskDefinitionKeyWithoutCascade), but form key does not.  This causes each set of the form key property to query the ACT_HI_TASKINST table to check to see if form key has changed.  Is this by design?  Should I create a JIRA ticket for this?