[
http://jira.jboss.com/jira/browse/JBPM-831?page=all ]
Tom Baeyens reopened JBPM-831:
------------------------------
ah.
that makes sense.
reopened and scheduled for 3.3 (since it is a database schema update)
by that time, we will still evaluate impact on the database schema migration and evaluate
if it is worthed.
avoid using default id generator
--------------------------------
Key: JBPM-831
URL:
http://jira.jboss.com/jira/browse/JBPM-831
Project: JBoss jBPM
Issue Type: Feature Request
Components: Core Engine
Affects Versions: jBPM 3.1.2
Environment: The problem is common to all platform.
Issue is identifed on Oracle 9.1 specifically.
Reporter: Wenbo Zhu
Assigned To: Tom Baeyens
Fix For: jBPM 3.3
The Id generator should be named explicitly, which is currently not.
<id name="id" column="ID_"><generator
class="native" /></id>
This will introdcue issue when jbpm schema has to be updated (dropped, e.g.) as the db
may be shared with other apps that uses default hibernate id generator too .. in case of
Oracle, it's "hibernate_sequence".
- Wenbo
--
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