-
1. Re: oracle : one single sequence for all jbpm tables under
ecompositor Jun 9, 2007 4:41 PM (in response to gogoasa)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. -
2. Re: oracle : one single sequence for all jbpm tables under
gogoasa Jun 10, 2007 8:45 AM (in response to 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). -
3. Re: oracle : one single sequence for all jbpm tables under
kukeltje Jun 10, 2007 1:34 PM (in response to gogoasa)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.
-
4. Re: oracle : one single sequence for all jbpm tables under
gogoasa Jun 11, 2007 4:43 AM (in response to gogoasa)Jira created : http://jira.jboss.com/jira/browse/JBPM-982