[jboss-jira] [JBoss JIRA] Closed: (JBPM-982) oracle : one single sequence for all jbpm tables

Mon Sep 3 05:00:18 EDT 2007

     [ http://jira.jboss.com/jira/browse/JBPM-982?page=all ]

Tom Baeyens closed JBPM-982.
----------------------------

    Fix Version/s:     (was: jBPM jPDL 3.2.2)
       Resolution: Rejected

your argumentation makes me question wether the db id should be shown in the web console.  there it is questionable.  but without an id, sometimes people might have many similar tasks in their task list.  then they see many identical rows.  which is equally inconvenient as having gaps in the sequence ids.

using a business key is the better solution then using different sequences.  many dbs don't even guarantee that subsequently generated ids will be successive numbers.

> oracle : one single sequence for all jbpm tables
> ------------------------------------------------
>
>                 Key: JBPM-982
>                 URL: http://jira.jboss.com/jira/browse/JBPM-982
>             Project: JBoss jBPM
>          Issue Type: Bug
>          Components: Core Engine
>    Affects Versions: jBPM jPDL 3.2
>         Environment: jBPM persisted in Oracle database
>            Reporter: Adrian Dimulescu
>         Assigned To: Tom Baeyens
>         Attachments: jbpm-different-sequences-names.patch.gz
>
>
> 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_TASK 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).
> The 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).
> Ronald van Kuijk says: jbpm 3.2.1 (don't know about 3.2) has a real business key. That could/should be used in the next console. 

-- 
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