[jboss-jira] [JBoss JIRA] Reopened: (JBPM-913) ProcessBean.startInstance does not set ProcessInstance.key, causing second process start for any user to fail

[ http://jira.jboss.com/jira/browse/JBPM-913?page=all ] David Lloyd reopened JBPM-913: ------------------------------ Yes, I know these databases allow null values in a constraint column. But the semantics work like this: If KEY_ is null and PROCESSDEFINITION_ is null, no entry is made into the unique index. THIS is the behavior that matches what you are talking about. If KEY_ is null and PROCESSDEFINITION_ is NOT null, an entry is made into the index with just the process definition ID. Since KEY_ is null, that part of the index is "blank". Therefore an insert of another process instance with a process definition but no key will cause a constraint violation. That's why I suggested that if this constraint is to exist in any form, then there should be a single column that is null unless both the key and process definition is specified, in which case the string value of the column would be something like "123:ProcessKey" where 123 is the process definition ID. Otherwise this constraint should be removed. -- 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