[
https://jira.jboss.org/jira/browse/JBPM-2369?page=com.atlassian.jira.plug...
]
Alejandro Guizar updated JBPM-2369:
-----------------------------------
Switching to CLOB columns allows jBPM to run on a standard 4KB page-size DB2 tablespace
efficiently (37 instances/second as measured by SimplePerformanceTest). This should become
the supported configuration.
Allow easy switching between VARCHAR(4000) and TEXT/CLOB
--------------------------------------------------------
Key: JBPM-2369
URL:
https://jira.jboss.org/jira/browse/JBPM-2369
Project: JBoss jBPM
Issue Type: Task
Components: Runtime Engine
Reporter: Alejandro Guizar
Assignee: Alejandro Guizar
Fix For: jBPM 3.2.7
Original Estimate: 0 minutes
Remaining Estimate: 0 minutes
DB2 restricts the max row length to be less than the page size, even if the max length is
never reached in practice. The "table per class hierarchy" mapping strategy is
particularly affected by this restriction, as the combined columns of all subclasses
easily add up to an excessive length. In the case of the JBPM_LOG table, the required page
size under DB2 is 32KB.
For this reason it is desirable that end users can easily switch from the on-row type
VARCHAR to the off-row type TEXT/CLOB. Such a switch would benefit other databases as
well, provided it is possible for users to upgrade their existing database schema. One
situation where switching would be helpful is JBPM-2057.
--
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