why the single hibernate oracle sequence

[erciped]

Hi

Why does the hibernate only use the single oracle database sequence? We tend to use a separate sequence for every table unless we need to have uniqueness across multiple tables.

Does jBPM use the sequence value in any way? We had the same problem when we used OS Workflow in that the whole framework schema used one sequence [hibernate_sequence] and the application code also required the separate entities to have unique identifiers. We thought that was odd and only found out when we were cleaning up our hibernate mappings and creating separate sequences and OSWorkflow started acting funny. Nast bug.

Any help would be appreciated as we want to have separate sequences for each table. We don't mind some table sharing a sequence if necessary.

Eric

[jbarrez]

If you take a look at the jBPM hbms, you'll see that the id generator is set to 'native'. According to Hibernate doc, this means that indeed only one sequence will be used...

You can change this by changing the hbms of jBPM.
See http://www.hibernate.org/296.html for more information.

[erciped]

Thanks jbarrez. I am aware I can change it but the question is

will changing the model to use multiple sequences have any adverse affects in jBPM

I don't want to get any unexpected behavior like I did with OSWorkflow

[jbarrez]

I haven't tried it yet, but I don't see any problems. After all, Hibernate will handle the primary key for jBPM and I don't see any problems in that.