oracle : one single sequence for all jbpm tables under

[gogoasa]

If I understand correctly, in order to generate table ids on Oracle, the hibernate-generated DDL specifies one single sequence :

create sequence hibernate_sequence;

That means that successive values for, say, deployed processes JBPM_PROCESSDEFINITION can be as far away from each other as 1 from 15000 (given that the same sequence generator is used for the lines in the JBPM_LOG table too)

Do you feel that this is not a problem, is there a way to work around it or is it simply my imperfect configuring & compiling the current CVS ?

Thank you.

[ecompositor]

If there is a burning reason to have different sequence_numbers for different tables. you can create multiple sequences and modify the hibernate config files for each table.

It is easist to leave it as is and think of the id's as correlation ids that have no relationship other than to find the correct instance.

[gogoasa]

The only problem is that IDs do have business meaning, at least as far as the JBPM console is concerned : the ID's are shown there in order to identify processes, tasks etc.

That may be confusing for users as they may wonder whatever happened to the tasks between 19 (last he solved) and 57 (the next one).

[kukeltje]

Good point regarding the gaps in processinstances this way. That does not mean they have a real business meaning. jbpm 3.2.1 (don't know about 3.2) has a real business key. That could/should be used in the next console. Please file a jira issue for this 'gap' thing.

[gogoasa]

Jira created : http://jira.jboss.com/jira/browse/JBPM-982