[JBoss JIRA] Created: (JBPM-2017) STRINGVALUE_ column in JBPM_VARIABLEINSTANCE table should be text, not varchar(255)
8:50 a.m.
STRINGVALUE_ column in JBPM_VARIABLEINSTANCE table should be text, not varchar(255)
-----------------------------------------------------------------------------------
Key: JBPM-2017
URL: https://jira.jboss.org/jira/browse/JBPM-2017
Project: JBoss jBPM
Issue Type: Task
Security Level: Public (Everyone can see)
Reporter: Alejandro Guizar
In JBPM-1849, Thomas enumerated the current incompatibilites against 3.2.2. One of them
is:
< create table JBPM_VARIABLEINSTANCE (... STRINGVALUE_ varchar(4000) null, ...)
create table JBPM_VARIABLEINSTANCE (... STRINGVALUE_ varchar(255)
null, ...)
The new type should be text, not varchar. This is related to the fact that the
STRINGVALUE_ column is shared between StringInstance.hbm.xml and
HibernateStringInstance.hbm.xml, both in
modules/core/src/main/resources/org/jbpm/context/exe/variableinstance/.
HibernateStringinstance.hbm.xml does not specify type="text".
--
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
8:52 a.m.
New subject: [JBoss JIRA] Updated: (JBPM-2017) STRINGVALUE_ column in JBPM_VARIABLEINSTANCE table should be text, not varchar(255)
[
https://jira.jboss.org/jira/browse/JBPM-2017?page=com.atlassian.jira.plug...
]
Alejandro Guizar updated JBPM-2017:
-----------------------------------
Component/s: Core Engine
Fix Version/s: jBPM-3.2.5.SP1
jBPM 3.2.6 GA
Affects Version/s: jBPM 3.2.5 GA
jBPM 3.2.4 GA
STRINGVALUE_ column in JBPM_VARIABLEINSTANCE table should be text,
not varchar(255)
-----------------------------------------------------------------------------------
Key: JBPM-2017
URL: https://jira.jboss.org/jira/browse/JBPM-2017
Project: JBoss jBPM
Issue Type: Task
Security Level: Public(Everyone can see)
Components: Core Engine
Affects Versions: jBPM 3.2.4 GA, jBPM 3.2.5 GA
Reporter: Alejandro Guizar
Fix For: jBPM-3.2.5.SP1, jBPM 3.2.6 GA
In JBPM-1849, Thomas enumerated the current incompatibilites against 3.2.2. One of them
is:
< create table JBPM_VARIABLEINSTANCE (... STRINGVALUE_ varchar(4000) null, ...)
> create table JBPM_VARIABLEINSTANCE (... STRINGVALUE_ varchar(255) null, ...)
The new type should be text, not varchar. This is related to the fact that the
STRINGVALUE_ column is shared between StringInstance.hbm.xml and
HibernateStringInstance.hbm.xml, both in
modules/core/src/main/resources/org/jbpm/context/exe/variableinstance/.
HibernateStringinstance.hbm.xml does not specify type="text".
--
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:55 a.m.
New subject: [JBoss JIRA] Assigned: (JBPM-2017) STRINGVALUE_ column in JBPM_VARIABLEINSTANCE table should be text, not varchar(255)
[
https://jira.jboss.org/jira/browse/JBPM-2017?page=com.atlassian.jira.plug...
]
Alejandro Guizar reassigned JBPM-2017:
--------------------------------------
Assignee: Alejandro Guizar
STRINGVALUE_ column in JBPM_VARIABLEINSTANCE table should be text,
not varchar(255)
-----------------------------------------------------------------------------------
Key: JBPM-2017
URL: https://jira.jboss.org/jira/browse/JBPM-2017
Project: JBoss jBPM
Issue Type: Task
Security Level: Public(Everyone can see)
Components: Core Engine
Affects Versions: jBPM 3.2.4 GA, jBPM 3.2.5 GA
Reporter: Alejandro Guizar
Assignee: Alejandro Guizar
Fix For: jBPM-3.2.5.SP1, jBPM 3.2.6 GA
In JBPM-1849, Thomas enumerated the current incompatibilites against 3.2.2. One of them
is:
< create table JBPM_VARIABLEINSTANCE (... STRINGVALUE_ varchar(4000) null, ...)
> create table JBPM_VARIABLEINSTANCE (... STRINGVALUE_ varchar(255) null, ...)
The new type should be text, not varchar. This is related to the fact that the
STRINGVALUE_ column is shared between StringInstance.hbm.xml and
HibernateStringInstance.hbm.xml, both in
modules/core/src/main/resources/org/jbpm/context/exe/variableinstance/.
HibernateStringinstance.hbm.xml does not specify type="text".
--
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
11:07 a.m.
New subject: [JBoss JIRA] Work started: (JBPM-2017) STRINGVALUE_ column in JBPM_VARIABLEINSTANCE table should be text, not varchar(255)
[
https://jira.jboss.org/jira/browse/JBPM-2017?page=com.atlassian.jira.plug...
]
Work on JBPM-2017 started by Alejandro Guizar.
STRINGVALUE_ column in JBPM_VARIABLEINSTANCE table should be text,
not varchar(255)
-----------------------------------------------------------------------------------
Key: JBPM-2017
URL: https://jira.jboss.org/jira/browse/JBPM-2017
Project: JBoss jBPM
Issue Type: Task
Security Level: Public(Everyone can see)
Components: Core Engine
Affects Versions: jBPM 3.2.4 GA, jBPM 3.2.5 GA
Reporter: Alejandro Guizar
Assignee: Alejandro Guizar
Fix For: jBPM-3.2.5.SP1, jBPM 3.2.6 GA
In JBPM-1849, Thomas enumerated the current incompatibilites against 3.2.2. One of them
is:
< create table JBPM_VARIABLEINSTANCE (... STRINGVALUE_ varchar(4000) null, ...)
> create table JBPM_VARIABLEINSTANCE (... STRINGVALUE_ varchar(255) null, ...)
The new type should be text, not varchar. This is related to the fact that the
STRINGVALUE_ column is shared between StringInstance.hbm.xml and
HibernateStringInstance.hbm.xml, both in
modules/core/src/main/resources/org/jbpm/context/exe/variableinstance/.
HibernateStringinstance.hbm.xml does not specify type="text".
--
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
7:28 p.m.
New subject: [JBoss JIRA] Resolved: (JBPM-2017) STRINGVALUE_ column in JBPM_VARIABLEINSTANCE table should be text, not varchar(255)
[
https://jira.jboss.org/jira/browse/JBPM-2017?page=com.atlassian.jira.plug...
]
Alejandro Guizar resolved JBPM-2017.
------------------------------------
Resolution: Done
Corrected HibernateStringInstance.hbm.xml, made the correction work for Sybase/jConnect,
wrote test case.
STRINGVALUE_ column in JBPM_VARIABLEINSTANCE table should be text,
not varchar(255)
-----------------------------------------------------------------------------------
Key: JBPM-2017
URL: https://jira.jboss.org/jira/browse/JBPM-2017
Project: JBoss jBPM
Issue Type: Task
Security Level: Public(Everyone can see)
Components: Core Engine
Affects Versions: jBPM 3.2.4 GA, jBPM 3.2.5 GA
Reporter: Alejandro Guizar
Assignee: Alejandro Guizar
Fix For: jBPM-3.2.5.SP1, jBPM 3.2.6 GA
In JBPM-1849, Thomas enumerated the current incompatibilites against 3.2.2. One of them
is:
< create table JBPM_VARIABLEINSTANCE (... STRINGVALUE_ varchar(4000) null, ...)
> create table JBPM_VARIABLEINSTANCE (... STRINGVALUE_ varchar(255) null, ...)
The new type should be text, not varchar. This is related to the fact that the
STRINGVALUE_ column is shared between StringInstance.hbm.xml and
HibernateStringInstance.hbm.xml, both in
modules/core/src/main/resources/org/jbpm/context/exe/variableinstance/.
HibernateStringinstance.hbm.xml does not specify type="text".
--
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:06 a.m.
New subject: [JBoss JIRA] Commented: (JBPM-2017) STRINGVALUE_ column in JBPM_VARIABLEINSTANCE table should be text, not varchar(255)
[
https://jira.jboss.org/jira/browse/JBPM-2017?page=com.atlassian.jira.plug...
]
Thomas Diesler commented on JBPM-2017:
--------------------------------------
Current incompatibilities (based on sybase.sql) are
diff jbpm-3.2.2/jbpm.jpdl.sybase.sql jbpm-3.2.5.SP1/jbpm.jpdl.sybase.sql
< create table JBPM_ACTION (... EXPRESSION_ varchar(4000) null, ...)
create table JBPM_ACTION (... EXPRESSION_ text null, ...)
< create table JBPM_COMMENT (... MESSAGE_ varchar(4000) null, ...)
create table JBPM_COMMENT (... MESSAGE_ text null, ...)
< create table JBPM_DELEGATION (... CLASSNAME_ varchar(4000) null, CONFIGURATION_
varchar(4000) null, ...)
create table JBPM_DELEGATION (... CLASSNAME_ text null,
CONFIGURATION_ text null, ...)
< create table JBPM_EXCEPTIONHANDLER (... EXCEPTIONCLASSNAME_ varchar(4000) null, ...)
create table JBPM_EXCEPTIONHANDLER (... EXCEPTIONCLASSNAME_ text
null, ...)
< create table JBPM_JOB (... EXCEPTION_ varchar(4000) null, ...)
create table JBPM_JOB (... EXCEPTION_ text null, ...)
< create table JBPM_LOG (... MESSAGE_ varchar(4000) null, ... EXCEPTION_ varchar(4000)
null, ... OLDSTRINGVALUE_ varchar(4000) null, NEWSTRINGVALUE_ varchar(4000) null, ...)
create table JBPM_LOG (... MESSAGE_ text null, ...
EXCEPTION_ text null, ... OLDSTRINGVALUE_ text null, NEWSTRINGVALUE_
text null, ...)
< create table JBPM_MODULEDEFINITION (... NAME_ varchar(4000) null, ...)
create table JBPM_MODULEDEFINITION (... NAME_ varchar(255) null,
...)
< create table JBPM_NODE (... DESCRIPTION_ varchar(4000) null, ...)
create table JBPM_NODE (... DESCRIPTION_ text null, ...
PARENTLOCKMODE_ varchar(255) null, ...)
< create table JBPM_PROCESSDEFINITION (... DESCRIPTION_ varchar(4000) null, ...)
create table JBPM_PROCESSDEFINITION (... DESCRIPTION_ text null,
...)
< create table JBPM_TASK (... DESCRIPTION_ varchar(4000) null, ...)
create table JBPM_TASK (... DESCRIPTION_ text null, ...)
< create table JBPM_TASKINSTANCE (... DESCRIPTION_ varchar(4000) null, ...)
create table JBPM_TASKINSTANCE (... DESCRIPTION_ text null,
...)
< create table JBPM_TRANSITION (... DESCRIPTION_ varchar(4000) null, ...)
create table JBPM_TRANSITION (... DESCRIPTION_ text null,
...)
< create table JBPM_VARIABLEINSTANCE (... STRINGVALUE_ varchar(4000) null, ...)
create table JBPM_VARIABLEINSTANCE (... STRINGVALUE_ text null,
...)
STRINGVALUE_ column in JBPM_VARIABLEINSTANCE table should be text,
not varchar(255)
-----------------------------------------------------------------------------------
Key: JBPM-2017
URL: https://jira.jboss.org/jira/browse/JBPM-2017
Project: JBoss jBPM
Issue Type: Task
Security Level: Public(Everyone can see)
Components: Core Engine
Affects Versions: jBPM 3.2.4 GA, jBPM 3.2.5 GA
Reporter: Alejandro Guizar
Assignee: Alejandro Guizar
Fix For: jBPM-3.2.5.SP1, jBPM 3.2.6 GA
In JBPM-1849, Thomas enumerated the current incompatibilites against 3.2.2. One of them
is:
< create table JBPM_VARIABLEINSTANCE (... STRINGVALUE_ varchar(4000) null, ...)
> create table JBPM_VARIABLEINSTANCE (... STRINGVALUE_ varchar(255) null, ...)
The new type should be text, not varchar. This is related to the fact that the
STRINGVALUE_ column is shared between StringInstance.hbm.xml and
HibernateStringInstance.hbm.xml, both in
modules/core/src/main/resources/org/jbpm/context/exe/variableinstance/.
HibernateStringinstance.hbm.xml does not specify type="text".
--
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:08 a.m.
New subject: [JBoss JIRA] Reopened: (JBPM-2017) STRINGVALUE_ column in JBPM_VARIABLEINSTANCE table should be text, not varchar(255)
[
https://jira.jboss.org/jira/browse/JBPM-2017?page=com.atlassian.jira.plug...
]
Thomas Diesler reopened JBPM-2017:
----------------------------------
Assignee: Thomas Diesler (was: Alejandro Guizar)
This is still not compatible
< create table JBPM_MODULEDEFINITION (... NAME_ varchar(4000) null, ...)
create table JBPM_MODULEDEFINITION (... NAME_ varchar(255) null,
...)
STRINGVALUE_ column in JBPM_VARIABLEINSTANCE table should be text,
not varchar(255)
-----------------------------------------------------------------------------------
Key: JBPM-2017
URL: https://jira.jboss.org/jira/browse/JBPM-2017
Project: JBoss jBPM
Issue Type: Task
Security Level: Public(Everyone can see)
Components: Core Engine
Affects Versions: jBPM 3.2.4 GA, jBPM 3.2.5 GA
Reporter: Alejandro Guizar
Assignee: Thomas Diesler
Fix For: jBPM-3.2.5.SP1, jBPM 3.2.6 GA
In JBPM-1849, Thomas enumerated the current incompatibilites against 3.2.2. One of them
is:
< create table JBPM_VARIABLEINSTANCE (... STRINGVALUE_ varchar(4000) null, ...)
> create table JBPM_VARIABLEINSTANCE (... STRINGVALUE_ varchar(255) null, ...)
The new type should be text, not varchar. This is related to the fact that the
STRINGVALUE_ column is shared between StringInstance.hbm.xml and
HibernateStringInstance.hbm.xml, both in
modules/core/src/main/resources/org/jbpm/context/exe/variableinstance/.
HibernateStringinstance.hbm.xml does not specify type="text".
--
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:08 a.m.
New subject: [JBoss JIRA] Work started: (JBPM-2017) STRINGVALUE_ column in JBPM_VARIABLEINSTANCE table should be text, not varchar(255)
[
https://jira.jboss.org/jira/browse/JBPM-2017?page=com.atlassian.jira.plug...
]
Work on JBPM-2017 started by Thomas Diesler.
STRINGVALUE_ column in JBPM_VARIABLEINSTANCE table should be text,
not varchar(255)
-----------------------------------------------------------------------------------
Key: JBPM-2017
URL: https://jira.jboss.org/jira/browse/JBPM-2017
Project: JBoss jBPM
Issue Type: Task
Security Level: Public(Everyone can see)
Components: Core Engine
Affects Versions: jBPM 3.2.4 GA, jBPM 3.2.5 GA
Reporter: Alejandro Guizar
Assignee: Thomas Diesler
Fix For: jBPM-3.2.5.SP1, jBPM 3.2.6 GA
In JBPM-1849, Thomas enumerated the current incompatibilites against 3.2.2. One of them
is:
< create table JBPM_VARIABLEINSTANCE (... STRINGVALUE_ varchar(4000) null, ...)
> create table JBPM_VARIABLEINSTANCE (... STRINGVALUE_ varchar(255) null, ...)
The new type should be text, not varchar. This is related to the fact that the
STRINGVALUE_ column is shared between StringInstance.hbm.xml and
HibernateStringInstance.hbm.xml, both in
modules/core/src/main/resources/org/jbpm/context/exe/variableinstance/.
HibernateStringinstance.hbm.xml does not specify type="text".
--
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:19 a.m.
New subject: [JBoss JIRA] Resolved: (JBPM-2017) STRINGVALUE_ column in JBPM_VARIABLEINSTANCE table should be text, not varchar(255)
[
https://jira.jboss.org/jira/browse/JBPM-2017?page=com.atlassian.jira.plug...
]
Thomas Diesler resolved JBPM-2017.
----------------------------------
Resolution: Done
Running org.jbpm.jbpm2017.JBPM2017Test
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 6.463 sec
STRINGVALUE_ column in JBPM_VARIABLEINSTANCE table should be text,
not varchar(255)
-----------------------------------------------------------------------------------
Key: JBPM-2017
URL: https://jira.jboss.org/jira/browse/JBPM-2017
Project: JBoss jBPM
Issue Type: Task
Security Level: Public(Everyone can see)
Components: Core Engine
Affects Versions: jBPM 3.2.4 GA, jBPM 3.2.5 GA
Reporter: Alejandro Guizar
Assignee: Thomas Diesler
Fix For: jBPM-3.2.5.SP1, jBPM 3.2.6 GA
In JBPM-1849, Thomas enumerated the current incompatibilites against 3.2.2. One of them
is:
< create table JBPM_VARIABLEINSTANCE (... STRINGVALUE_ varchar(4000) null, ...)
> create table JBPM_VARIABLEINSTANCE (... STRINGVALUE_ varchar(255) null, ...)
The new type should be text, not varchar. This is related to the fact that the
STRINGVALUE_ column is shared between StringInstance.hbm.xml and
HibernateStringInstance.hbm.xml, both in
modules/core/src/main/resources/org/jbpm/context/exe/variableinstance/.
HibernateStringinstance.hbm.xml does not specify type="text".
--
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
5800
days inactive
5802
days old
8 comments
2 participants
participants (2)
-
Alejandro Guizar (JIRA) -
Thomas Diesler (JIRA)