[JBoss JIRA] Created: (JBPM-2765) With the introduction of the id generator sql-scripts (${jbpm.home}/install/src/db/create) were not updated
1:51 a.m.
With the introduction of the id generator sql-scripts (${jbpm.home}/install/src/db/create)
were not updated
-----------------------------------------------------------------------------------------------------------
Key: JBPM-2765
URL: https://jira.jboss.org/jira/browse/JBPM-2765
Project: jBPM
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: jBPM 4.3
Environment: Databases HSQLDB, MySQL, Oracle, PostgrasSql: if database tables
where created using the sql-scripts in ${jbpm.home}/install/src/db/create
Reporter: Jan Scherf
Fix For: jBPM 4.4
org.jbpm.pvm.internal.model.ExecutionImpl.save() crashs with database-error.
reason:
- DatabaseIdComposer.createId(...) produces datatype string
- but sql-Skripts create dbid-colums whose datatype is integer
__________________________________________________________________________________________
See more Details on: http://community.jboss.org/message/521822
The reason of this problem can be found in
org.jbpm.pvm.internal.id.DatabaseIdComposer.createId(...) which is called in
org.jbpm.pvm.internal.model.ExecutionImpl.save() to initialize ExecutionImpl.dbid.
Property dbid is mapped to database table JBPM4_EXECUTION (see: jbpm.execution.hbm.xml).
As you can see in sql-files in ${jbpm.home}/src/db/create, the database-field-datatype of
property DBID_ is a kind of integer. But DatabaseIdComposer.createId(...) produces String
...
It seems that with the introduction of the id generator these scripts were not updated.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:53 a.m.
New subject: [JBoss JIRA] Updated: (JBPM-2765) With the introduction of the id generator sql-scripts (${jbpm.home}/install/src/db/create) were not updated
[
https://jira.jboss.org/jira/browse/JBPM-2765?page=com.atlassian.jira.plug...
]
Jan Scherf updated JBPM-2765:
-----------------------------
Workaround Description:
Workaround 1:
- Letting hibernate do the creation of database tables.
Workaround 2 (no good idea, because "signalProcessInstance" can't find
ProcessInstance by ExecutionId):
- Use integer-values as "key" in you processdefinition.
e.g. use <process description="myDescription" key="123"
name="myProcess" version="0"
xmlns="http://jbpm.org/4.3/jpdl">
instead of <process description="myDescription" key="anyString"
name="myProcess" version="0"
xmlns="http://jbpm.org/4.3/jpdl">
was:
Workaround 1:
- Use integer-values as "key" in you processdefinition.
e.g. use <process description="myDescription" key="123"
name="myProcess" version="0"
xmlns="http://jbpm.org/4.3/jpdl">
instead of <process description="myDescription" key="anyString"
name="myProcess" version="0"
xmlns="http://jbpm.org/4.3/jpdl">
Workaround 2:
- Letting hibernate do the 'upgrade' might work.
Priority: Minor (was: Major)
With the introduction of the id generator sql-scripts
(${jbpm.home}/install/src/db/create) were not updated
-----------------------------------------------------------------------------------------------------------
Key: JBPM-2765
URL: https://jira.jboss.org/jira/browse/JBPM-2765
Project: jBPM
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: jBPM 4.3
Environment: Databases HSQLDB, MySQL, Oracle, PostgrasSql: if database tables
where created using the sql-scripts in ${jbpm.home}/install/src/db/create
Reporter: Jan Scherf
Priority: Minor
Fix For: jBPM 4.4
org.jbpm.pvm.internal.model.ExecutionImpl.save() crashs with database-error.
reason:
- DatabaseIdComposer.createId(...) produces datatype string
- but sql-Skripts create dbid-colums whose datatype is integer
__________________________________________________________________________________________
See more Details on: http://community.jboss.org/message/521822
The reason of this problem can be found in
org.jbpm.pvm.internal.id.DatabaseIdComposer.createId(...) which is called in
org.jbpm.pvm.internal.model.ExecutionImpl.save() to initialize ExecutionImpl.dbid.
Property dbid is mapped to database table JBPM4_EXECUTION (see: jbpm.execution.hbm.xml).
As you can see in sql-files in ${jbpm.home}/src/db/create, the database-field-datatype of
property DBID_ is a kind of integer. But DatabaseIdComposer.createId(...) produces String
...
It seems that with the introduction of the id generator these scripts were not updated.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:40 p.m.
New subject: [JBoss JIRA] Commented: (JBPM-2765) With the introduction of the id generator sql-scripts (${jbpm.home}/install/src/db/create) were not updated
[
https://jira.jboss.org/jira/browse/JBPM-2765?page=com.atlassian.jira.plug...
]
Huisheng Xu commented on JBPM-2765:
-----------------------------------
I don't think this is a bug. Because the DatabaseIdComposer is used to create a
unique id for Execution. But this id is related to the ID_ column of JBPM4_EXECUTION,
its datatype is string.
The DBID_ column is related to the dbid column of JBPM4_EXECUTION and it's datatype is
integer.
So I think this issue should be closed.
With the introduction of the id generator sql-scripts
(${jbpm.home}/install/src/db/create) were not updated
-----------------------------------------------------------------------------------------------------------
Key: JBPM-2765
URL: https://jira.jboss.org/jira/browse/JBPM-2765
Project: jBPM
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: jBPM 4.3
Environment: Databases HSQLDB, MySQL, Oracle, PostgrasSql: if database tables
where created using the sql-scripts in ${jbpm.home}/install/src/db/create
Reporter: Jan Scherf
Priority: Minor
Fix For: jBPM 4.4
org.jbpm.pvm.internal.model.ExecutionImpl.save() crashs with database-error.
reason:
- DatabaseIdComposer.createId(...) produces datatype string
- but sql-Skripts create dbid-colums whose datatype is integer
__________________________________________________________________________________________
See more Details on: http://community.jboss.org/message/521822
The reason of this problem can be found in
org.jbpm.pvm.internal.id.DatabaseIdComposer.createId(...) which is called in
org.jbpm.pvm.internal.model.ExecutionImpl.save() to initialize ExecutionImpl.dbid.
Property dbid is mapped to database table JBPM4_EXECUTION (see: jbpm.execution.hbm.xml).
As you can see in sql-files in ${jbpm.home}/src/db/create, the database-field-datatype of
property DBID_ is a kind of integer. But DatabaseIdComposer.createId(...) produces String
...
It seems that with the introduction of the id generator these scripts were not updated.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
1:34 p.m.
New subject: [JBoss JIRA] Commented: (JBPM-2765) With the introduction of the id generator sql-scripts (${jbpm.home}/install/src/db/create) were not updated
[
https://jira.jboss.org/jira/browse/JBPM-2765?page=com.atlassian.jira.plug...
]
Sebastian Schneider commented on JBPM-2765:
-------------------------------------------
I don't understand this issue completely. In what way should SQL scripts have been
changed after the introduction of the DatabaseIdComposer? As someone stated on th forums
I'd prefer to use a Hibernate sequence anyway.
With the introduction of the id generator sql-scripts
(${jbpm.home}/install/src/db/create) were not updated
-----------------------------------------------------------------------------------------------------------
Key: JBPM-2765
URL: https://jira.jboss.org/jira/browse/JBPM-2765
Project: jBPM
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: jBPM 4.3
Environment: Databases HSQLDB, MySQL, Oracle, PostgrasSql: if database tables
where created using the sql-scripts in ${jbpm.home}/install/src/db/create
Reporter: Jan Scherf
Priority: Minor
Fix For: jBPM 4.4
org.jbpm.pvm.internal.model.ExecutionImpl.save() crashs with database-error.
reason:
- DatabaseIdComposer.createId(...) produces datatype string
- but sql-Skripts create dbid-colums whose datatype is integer
__________________________________________________________________________________________
See more Details on: http://community.jboss.org/message/521822
The reason of this problem can be found in
org.jbpm.pvm.internal.id.DatabaseIdComposer.createId(...) which is called in
org.jbpm.pvm.internal.model.ExecutionImpl.save() to initialize ExecutionImpl.dbid.
Property dbid is mapped to database table JBPM4_EXECUTION (see: jbpm.execution.hbm.xml).
As you can see in sql-files in ${jbpm.home}/src/db/create, the database-field-datatype of
property DBID_ is a kind of integer. But DatabaseIdComposer.createId(...) produces String
...
It seems that with the introduction of the id generator these scripts were not updated.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
1:12 a.m.
New subject: [JBoss JIRA] Assigned: (JBPM-2765) With the introduction of the id generator sql-scripts (${jbpm.home}/install/src/db/create) were not updated
[
https://jira.jboss.org/jira/browse/JBPM-2765?page=com.atlassian.jira.plug...
]
Huisheng Xu reassigned JBPM-2765:
---------------------------------
Assignee: Huisheng Xu
With the introduction of the id generator sql-scripts
(${jbpm.home}/install/src/db/create) were not updated
-----------------------------------------------------------------------------------------------------------
Key: JBPM-2765
URL: https://jira.jboss.org/jira/browse/JBPM-2765
Project: jBPM
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: jBPM 4.3
Environment: Databases HSQLDB, MySQL, Oracle, PostgrasSql: if database tables
where created using the sql-scripts in ${jbpm.home}/install/src/db/create
Reporter: Jan Scherf
Assignee: Huisheng Xu
Priority: Minor
Fix For: jBPM 4.4
org.jbpm.pvm.internal.model.ExecutionImpl.save() crashs with database-error.
reason:
- DatabaseIdComposer.createId(...) produces datatype string
- but sql-Skripts create dbid-colums whose datatype is integer
__________________________________________________________________________________________
See more Details on: http://community.jboss.org/message/521822
The reason of this problem can be found in
org.jbpm.pvm.internal.id.DatabaseIdComposer.createId(...) which is called in
org.jbpm.pvm.internal.model.ExecutionImpl.save() to initialize ExecutionImpl.dbid.
Property dbid is mapped to database table JBPM4_EXECUTION (see: jbpm.execution.hbm.xml).
As you can see in sql-files in ${jbpm.home}/src/db/create, the database-field-datatype of
property DBID_ is a kind of integer. But DatabaseIdComposer.createId(...) produces String
...
It seems that with the introduction of the id generator these scripts were not updated.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:03 p.m.
New subject: [JBoss JIRA] Assigned: (JBPM-2765) With the introduction of the id generator sql-scripts (${jbpm.home}/install/src/db/create) were not updated
[
https://jira.jboss.org/jira/browse/JBPM-2765?page=com.atlassian.jira.plug...
]
Huisheng Xu reassigned JBPM-2765:
---------------------------------
Assignee: (was: Huisheng Xu)
Not sure whether this issue is a intallation bug. Later open a post in forum to discuss
this.
With the introduction of the id generator sql-scripts
(${jbpm.home}/install/src/db/create) were not updated
-----------------------------------------------------------------------------------------------------------
Key: JBPM-2765
URL: https://jira.jboss.org/jira/browse/JBPM-2765
Project: jBPM
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: jBPM 4.3
Environment: Databases HSQLDB, MySQL, Oracle, PostgrasSql: if database tables
where created using the sql-scripts in ${jbpm.home}/install/src/db/create
Reporter: Jan Scherf
Priority: Minor
Fix For: jBPM 4.4
org.jbpm.pvm.internal.model.ExecutionImpl.save() crashs with database-error.
reason:
- DatabaseIdComposer.createId(...) produces datatype string
- but sql-Skripts create dbid-colums whose datatype is integer
__________________________________________________________________________________________
See more Details on: http://community.jboss.org/message/521822
The reason of this problem can be found in
org.jbpm.pvm.internal.id.DatabaseIdComposer.createId(...) which is called in
org.jbpm.pvm.internal.model.ExecutionImpl.save() to initialize ExecutionImpl.dbid.
Property dbid is mapped to database table JBPM4_EXECUTION (see: jbpm.execution.hbm.xml).
As you can see in sql-files in ${jbpm.home}/src/db/create, the database-field-datatype of
property DBID_ is a kind of integer. But DatabaseIdComposer.createId(...) produces String
...
It seems that with the introduction of the id generator these scripts were not updated.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:16 a.m.
New subject: [JBoss JIRA] Commented: (JBPM-2765) With the introduction of the id generator sql-scripts (${jbpm.home}/install/src/db/create) were not updated
[
https://jira.jboss.org/browse/JBPM-2765?page=com.atlassian.jira.plugin.sy...
]
Huisheng Xu commented on JBPM-2765:
-----------------------------------
OK, After re-read the forum post, I understand what caused this problem.
If we use hibernate 3.1 or hibernate 3.2, we will get this problem. Normally, NamedQuery
should use id to the query, but if the hibernate version that we used is lower than
hibernate 3.3, then NamedQuery will convert id to dbid. Because the type of id is
VARCHAR, the type of dbid is BIGINT, then the exception occured. After upgrade
hibernate from lower to 3.3, this problem will be sovled.
With the introduction of the id generator sql-scripts
(${jbpm.home}/install/src/db/create) were not updated
-----------------------------------------------------------------------------------------------------------
Key: JBPM-2765
URL: https://jira.jboss.org/browse/JBPM-2765
Project: jBPM
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: jBPM 4.3
Environment: Databases HSQLDB, MySQL, Oracle, PostgrasSql: if database tables
where created using the sql-scripts in ${jbpm.home}/install/src/db/create
Reporter: Jan Scherf
Priority: Minor
Fix For: jBPM 4.4
org.jbpm.pvm.internal.model.ExecutionImpl.save() crashs with database-error.
reason:
- DatabaseIdComposer.createId(...) produces datatype string
- but sql-Skripts create dbid-colums whose datatype is integer
__________________________________________________________________________________________
See more Details on: http://community.jboss.org/message/521822
The reason of this problem can be found in
org.jbpm.pvm.internal.id.DatabaseIdComposer.createId(...) which is called in
org.jbpm.pvm.internal.model.ExecutionImpl.save() to initialize ExecutionImpl.dbid.
Property dbid is mapped to database table JBPM4_EXECUTION (see: jbpm.execution.hbm.xml).
As you can see in sql-files in ${jbpm.home}/src/db/create, the database-field-datatype of
property DBID_ is a kind of integer. But DatabaseIdComposer.createId(...) produces String
...
It seems that with the introduction of the id generator these scripts were not updated.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:55 a.m.
New subject: [JBoss JIRA] Commented: (JBPM-2765) With the introduction of the id generator sql-scripts (${jbpm.home}/install/src/db/create) were not updated
[
https://jira.jboss.org/browse/JBPM-2765?page=com.atlassian.jira.plugin.sy...
]
Alejandro Guizar commented on JBPM-2765:
----------------------------------------
Great deductive work Hui Sheng. In this particular case I feel compelled to rename field
ExecutionImpl.id to uid in order to allow jBPM 4.4 to run with Hibernate versions prior to
3.3. The Execution interface and the accessor methods would keep their existing names.
What are your thoughts on this?
With the introduction of the id generator sql-scripts
(${jbpm.home}/install/src/db/create) were not updated
-----------------------------------------------------------------------------------------------------------
Key: JBPM-2765
URL: https://jira.jboss.org/browse/JBPM-2765
Project: jBPM
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: jBPM 4.3
Environment: Databases HSQLDB, MySQL, Oracle, PostgrasSql: if database tables
where created using the sql-scripts in ${jbpm.home}/install/src/db/create
Reporter: Jan Scherf
Priority: Minor
Fix For: jBPM 4.4
org.jbpm.pvm.internal.model.ExecutionImpl.save() crashs with database-error.
reason:
- DatabaseIdComposer.createId(...) produces datatype string
- but sql-Skripts create dbid-colums whose datatype is integer
__________________________________________________________________________________________
See more Details on: http://community.jboss.org/message/521822
The reason of this problem can be found in
org.jbpm.pvm.internal.id.DatabaseIdComposer.createId(...) which is called in
org.jbpm.pvm.internal.model.ExecutionImpl.save() to initialize ExecutionImpl.dbid.
Property dbid is mapped to database table JBPM4_EXECUTION (see: jbpm.execution.hbm.xml).
As you can see in sql-files in ${jbpm.home}/src/db/create, the database-field-datatype of
property DBID_ is a kind of integer. But DatabaseIdComposer.createId(...) produces String
...
It seems that with the introduction of the id generator these scripts were not updated.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:25 a.m.
New subject: [JBoss JIRA] Commented: (JBPM-2765) With the introduction of the id generator sql-scripts (${jbpm.home}/install/src/db/create) were not updated
[
https://jira.jboss.org/browse/JBPM-2765?page=com.atlassian.jira.plugin.sy...
]
Huisheng Xu commented on JBPM-2765:
-----------------------------------
Hi Ajejandro, if we change to database schema, we should provide related upgrade sql and
do related test. At least we should test it both on hibernate 3.3 and lower version.
So if it cost too much times, I will suggest to delay this issue to next release.
With the introduction of the id generator sql-scripts
(${jbpm.home}/install/src/db/create) were not updated
-----------------------------------------------------------------------------------------------------------
Key: JBPM-2765
URL: https://jira.jboss.org/browse/JBPM-2765
Project: jBPM
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: jBPM 4.3
Environment: Databases HSQLDB, MySQL, Oracle, PostgrasSql: if database tables
where created using the sql-scripts in ${jbpm.home}/install/src/db/create
Reporter: Jan Scherf
Priority: Minor
Fix For: jBPM 4.4
org.jbpm.pvm.internal.model.ExecutionImpl.save() crashs with database-error.
reason:
- DatabaseIdComposer.createId(...) produces datatype string
- but sql-Skripts create dbid-colums whose datatype is integer
__________________________________________________________________________________________
See more Details on: http://community.jboss.org/message/521822
The reason of this problem can be found in
org.jbpm.pvm.internal.id.DatabaseIdComposer.createId(...) which is called in
org.jbpm.pvm.internal.model.ExecutionImpl.save() to initialize ExecutionImpl.dbid.
Property dbid is mapped to database table JBPM4_EXECUTION (see: jbpm.execution.hbm.xml).
As you can see in sql-files in ${jbpm.home}/src/db/create, the database-field-datatype of
property DBID_ is a kind of integer. But DatabaseIdComposer.createId(...) produces String
...
It seems that with the introduction of the id generator these scripts were not updated.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:35 a.m.
New subject: [JBoss JIRA] Commented: (JBPM-2765) With the introduction of the id generator sql-scripts (${jbpm.home}/install/src/db/create) were not updated
[
https://jira.jboss.org/browse/JBPM-2765?page=com.atlassian.jira.plugin.sy...
]
Huisheng Xu commented on JBPM-2765:
-----------------------------------
Sorry, Alejandro. Do you mean that if we could solve this problem be just change the id
field of executionimpl to uid?
I am not sure whether it is a bug of older hibernate, but if we want to jbpm4 running on
the hibernate which version lower than 3.3. Maybe We have to change all id field of
domain class. TaskImpl, UserImpl, GroupImpl, seems they all have the same problem.
With the introduction of the id generator sql-scripts
(${jbpm.home}/install/src/db/create) were not updated
-----------------------------------------------------------------------------------------------------------
Key: JBPM-2765
URL: https://jira.jboss.org/browse/JBPM-2765
Project: jBPM
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: jBPM 4.3
Environment: Databases HSQLDB, MySQL, Oracle, PostgrasSql: if database tables
where created using the sql-scripts in ${jbpm.home}/install/src/db/create
Reporter: Jan Scherf
Priority: Minor
Fix For: jBPM 4.4
org.jbpm.pvm.internal.model.ExecutionImpl.save() crashs with database-error.
reason:
- DatabaseIdComposer.createId(...) produces datatype string
- but sql-Skripts create dbid-colums whose datatype is integer
__________________________________________________________________________________________
See more Details on: http://community.jboss.org/message/521822
The reason of this problem can be found in
org.jbpm.pvm.internal.id.DatabaseIdComposer.createId(...) which is called in
org.jbpm.pvm.internal.model.ExecutionImpl.save() to initialize ExecutionImpl.dbid.
Property dbid is mapped to database table JBPM4_EXECUTION (see: jbpm.execution.hbm.xml).
As you can see in sql-files in ${jbpm.home}/src/db/create, the database-field-datatype of
property DBID_ is a kind of integer. But DatabaseIdComposer.createId(...) produces String
...
It seems that with the introduction of the id generator these scripts were not updated.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:07 a.m.
New subject: [JBoss JIRA] Commented: (JBPM-2765) With the introduction of the id generator sql-scripts (${jbpm.home}/install/src/db/create) were not updated
[
https://jira.jboss.org/browse/JBPM-2765?page=com.atlassian.jira.plugin.sy...
]
Huisheng Xu commented on JBPM-2765:
-----------------------------------
I test it again. If we use hibernate-3.2.1.ga and previous version of hibernate.
(including 3.2.1.ga). This error will occured. If we use hibernate-3.2.2.ga and later
versions of hibernate. (including 3.2.2.ga). This version will not occured.
With the introduction of the id generator sql-scripts
(${jbpm.home}/install/src/db/create) were not updated
-----------------------------------------------------------------------------------------------------------
Key: JBPM-2765
URL: https://jira.jboss.org/browse/JBPM-2765
Project: jBPM
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: jBPM 4.3
Environment: Databases HSQLDB, MySQL, Oracle, PostgrasSql: if database tables
where created using the sql-scripts in ${jbpm.home}/install/src/db/create
Reporter: Jan Scherf
Priority: Minor
Fix For: jBPM 4.4
org.jbpm.pvm.internal.model.ExecutionImpl.save() crashs with database-error.
reason:
- DatabaseIdComposer.createId(...) produces datatype string
- but sql-Skripts create dbid-colums whose datatype is integer
__________________________________________________________________________________________
See more Details on: http://community.jboss.org/message/521822
The reason of this problem can be found in
org.jbpm.pvm.internal.id.DatabaseIdComposer.createId(...) which is called in
org.jbpm.pvm.internal.model.ExecutionImpl.save() to initialize ExecutionImpl.dbid.
Property dbid is mapped to database table JBPM4_EXECUTION (see: jbpm.execution.hbm.xml).
As you can see in sql-files in ${jbpm.home}/src/db/create, the database-field-datatype of
property DBID_ is a kind of integer. But DatabaseIdComposer.createId(...) produces String
...
It seems that with the introduction of the id generator these scripts were not updated.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:17 a.m.
New subject: [JBoss JIRA] Updated: (JBPM-2765) With the introduction of the id generator sql-scripts (${jbpm.home}/install/src/db/create) were not updated
[
https://jira.jboss.org/browse/JBPM-2765?page=com.atlassian.jira.plugin.sy...
]
Huisheng Xu updated JBPM-2765:
------------------------------
Attachment: hibernate331.zip
After I modify the id field of ExecutionImpl(including jbpm.execution.hbm.xml), the error
still here. Please refer attachment.
So I think even if we want to support lower version of hibernate, we should delay this
issue to the next releasing.
With the introduction of the id generator sql-scripts
(${jbpm.home}/install/src/db/create) were not updated
-----------------------------------------------------------------------------------------------------------
Key: JBPM-2765
URL: https://jira.jboss.org/browse/JBPM-2765
Project: jBPM
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: jBPM 4.3
Environment: Databases HSQLDB, MySQL, Oracle, PostgrasSql: if database tables
where created using the sql-scripts in ${jbpm.home}/install/src/db/create
Reporter: Jan Scherf
Priority: Minor
Fix For: jBPM 4.4
Attachments: hibernate331.zip
org.jbpm.pvm.internal.model.ExecutionImpl.save() crashs with database-error.
reason:
- DatabaseIdComposer.createId(...) produces datatype string
- but sql-Skripts create dbid-colums whose datatype is integer
__________________________________________________________________________________________
See more Details on: http://community.jboss.org/message/521822
The reason of this problem can be found in
org.jbpm.pvm.internal.id.DatabaseIdComposer.createId(...) which is called in
org.jbpm.pvm.internal.model.ExecutionImpl.save() to initialize ExecutionImpl.dbid.
Property dbid is mapped to database table JBPM4_EXECUTION (see: jbpm.execution.hbm.xml).
As you can see in sql-files in ${jbpm.home}/src/db/create, the database-field-datatype of
property DBID_ is a kind of integer. But DatabaseIdComposer.createId(...) produces String
...
It seems that with the introduction of the id generator these scripts were not updated.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:54 p.m.
New subject: [JBoss JIRA] Updated: (JBPM-2765) DB schema creation scripts were not updated after the introduction of the id generator
[
https://jira.jboss.org/browse/JBPM-2765?page=com.atlassian.jira.plugin.sy...
]
Alejandro Guizar updated JBPM-2765:
-----------------------------------
Summary: DB schema creation scripts were not updated after the introduction of
the id generator (was: With the introduction of the id generator sql-scripts
(${jbpm.home}/install/src/db/create) were not updated)
Fix Version/s: jBPM 4.x
(was: jBPM 4.4)
Complexity: (was: Low)
Component/s: Runtime Engine
Deferring, jBPM 4.4 is already tagged. After thinking about it I no longer think it is a
good idea to rename fields just to be compatible with older Hibernate versions, unless
there is a very compelling reason to do so.
DB schema creation scripts were not updated after the introduction of
the id generator
--------------------------------------------------------------------------------------
Key: JBPM-2765
URL: https://jira.jboss.org/browse/JBPM-2765
Project: jBPM
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Runtime Engine
Affects Versions: jBPM 4.3
Environment: Databases HSQLDB, MySQL, Oracle, PostgrasSql: if database tables
where created using the sql-scripts in ${jbpm.home}/install/src/db/create
Reporter: Jan Scherf
Priority: Minor
Fix For: jBPM 4.x
Attachments: hibernate331.zip
org.jbpm.pvm.internal.model.ExecutionImpl.save() crashs with database-error.
reason:
- DatabaseIdComposer.createId(...) produces datatype string
- but sql-Skripts create dbid-colums whose datatype is integer
__________________________________________________________________________________________
See more Details on: http://community.jboss.org/message/521822
The reason of this problem can be found in
org.jbpm.pvm.internal.id.DatabaseIdComposer.createId(...) which is called in
org.jbpm.pvm.internal.model.ExecutionImpl.save() to initialize ExecutionImpl.dbid.
Property dbid is mapped to database table JBPM4_EXECUTION (see: jbpm.execution.hbm.xml).
As you can see in sql-files in ${jbpm.home}/src/db/create, the database-field-datatype of
property DBID_ is a kind of integer. But DatabaseIdComposer.createId(...) produces String
...
It seems that with the introduction of the id generator these scripts were not updated.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
5100
days inactive
5275
days old
12 comments
4 participants
participants (4)
-
Alejandro Guizar (JIRA) -
Huisheng Xu (JIRA)
-
Jan Scherf (JIRA)
-
Sebastian Schneider (JIRA)