Minor bug in activiti.oracle.create.engine.sql

As we transition to the new Hyland Community, some post links may be temporarily disrupted as we finalize redirects. We apologize for the inconvenience and are working to resolve this as quickly as possible. Details.

grchld

It seems the last statement in activiti.oracle.create.engine.sql has a misprint:

– see http://stackoverflow.com/questions/675398/how-can-i-constrain-multiple-columns-to-prevent-duplicates-but-ignore-null-value
create unique index ACT_UNIQ_RU_BUS_KEY on ACT_RU_EXECUTION
   (case when BUSINESS_KEY_ is null then null else PROC_DEF_ID_ end,
    case when BUSINESS_KEY_ is null then null else BUSINESS_KEY_ end);
‍‍‍‍‍‍

the second BUSINESS_KEY_ should be replaced with PROC_DEF_ID_

jbarrez

The sql looks indeed funny, but I believe it does what it must do: the two parameters both depend on the business key