[
https://issues.jboss.org/browse/JBPM-2031?page=com.atlassian.jira.plugin....
]
Alejandro Guizar updated JBPM-2031:
-----------------------------------
Original Estimate: 0 minutes
Remaining Estimate: 0 minutes
Fix Version/s: jBPM 3.2.10
(was: jBPM 3.2.x)
Some bidirectional associations do not use inverse="true"
---------------------------------------------------------
Key: JBPM-2031
URL:
https://issues.jboss.org/browse/JBPM-2031
Project: jBPM
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Runtime Engine
Affects Versions: jBPM 3.3.1 GA, jBPM 3.2.9
Environment: Tested with MySQL with query log enabled in JUnit.
Reporter: Tomasz Wysocki
Assignee: Alejandro Guizar
Priority: Critical
Fix For: jBPM 3.2.10
Original Estimate: 0 minutes
Remaining Estimate: 0 minutes
Currently couple of bidirectional associations do not use inverse="true" on
one-to-many side (collection)
The examples are
- ProcessInstance.instances
- CompositeLog.children
I'm sure there are more of them.
Lack of inverse="true" results in additional "UPDATE" statement being
issued by hibernate to create a relationship from a one-to-many side.
This is not necessary when java code is updating both ends of an association.
Some use-cases where lots of new processes are being created would see a performance
improvement.
CompositeLog logging overhead will decrease (only INSERT will be issued - no UPDATE)
Please consider reviewing all of your bidirectional associations with respect to this
optimization.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira