[jbpm-issues] [JBoss JIRA] Reopened: (JBPM-2018) StringInstance hbm configuration column length of 4000
[
https://jira.jboss.org/jira/browse/JBPM-2018?page=com.atlassian.jira.plug...
]
Alejandro Guizar reopened JBPM-2018:
------------------------------------
Assignee: Alejandro Guizar (was: Thomas Diesler)
Not a duplicate. JBPM-2017 is about the type of the JBPM_VARIABLEINSTANCE_.STRINGVALUE_
column. JBPM-2018 is about restoring the column length of 4000 for databases that, in
absence of an explicit length, limit text columns to 255 characters; for example, DB2.
Note that our current database axes, HSQLDB, MySQL, PostgreSQL and Sybase, do not honor
the length attribute. The 4000 limit does not appear anywhere in the resulting DDL
scripts.
StringInstance hbm configuration column length of 4000
------------------------------------------------------
Key: JBPM-2018
URL: https://jira.jboss.org/jira/browse/JBPM-2018
Project: JBoss jBPM
Issue Type: Bug
Affects Versions: jBPM 3.2.2
Reporter: Kevin Conner
Assignee: Alejandro Guizar
The reason for the discrepancy in the generated DDL files appears to be a conflict
between the hibernate definitions for HibernateStringInstance.hbm.xml,
StringInstance.hbm.xml and (potentially) JcrNodeInstance.hbm.xml.
Each of these VariableInstance subclasses map entries onto the JBPM_VARIABLEINSTANCE
using the same field, STRINGVALUE_, but only StringInstance.hbm.xml specifies the length.
The length is obviously being ignored when the DDL files are created as the
HIbernateStringInstance.hbm.xml is being loaded first.
--
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