[
http://jira.jboss.com/jira/browse/JBPM-736?page=comments#action_12341406 ]
Alejandro Guizar commented on JBPM-736:
---------------------------------------
The initial solution requires two delete statements to clear the logs. I tried setting the
CompositeLog.children association mapping to cascade the delete operation. I executed a
single delete statement to clear the top-level logs only. I expected cascading to clear
the child logs, but I still get a constraint violation.
jBPM 3.1 cascades all operations but deletes processLogs one at a time. I guess 2 deletes
are better than n :-) I'll keep the initial solution. I'm aware it fails when a
child log is a compositeLog itself. AFAIK, this situation never occurs.
constraint violation while deleting process instance
----------------------------------------------------
Key: JBPM-736
URL:
http://jira.jboss.com/jira/browse/JBPM-736
Project: JBoss jBPM
Issue Type: Bug
Components: Core Engine
Affects Versions: jBPM 3.0.4
Reporter: Alejandro Guizar
Assigned To: Alejandro Guizar
Priority: Critical
Methods testDeleteProcessInstanceWithVariables and testDeleteProcessDefinition in
GraphSessionDbTest fail with a constraint violation exception.
The children of compositeLogs prevent their parent from being deleted.
My initial solution is deleting processLogs with a non-null parent first. Afterwards,
delete the remaining logs. It seems to work.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira