[jbpm-issues] [JBoss JIRA] Resolved: (JBPM-396) Queries generated via hibernate are not compatible with Db2 for iSeries

Queries generated via hibernate are not compatible with Db2 for iSeries ----------------------------------------------------------------------- Key: JBPM-396 URL: http://jira.jboss.com/jira/browse/JBPM-396 Project: JBoss jBPM Issue Type: Bug Components: Core Engine Affects Versions: jBPM 3.0.1 Environment: Windows, DB2 UDB for iSeries Reporter: Paul Newport Assigned To: Tom Baeyens Essentially the problem is that because the hibernate mapping files specify column lengths for some string fields as 4000, these get created as varchars on the iSeries, as the iSeries varchar maximum is just under 32k. If JBPM does a query that results in many individual 4000 long varchars being requested to be returned, this blows DB2's limit of 32k for a result set width (ie, the sum of the column lengths for each non LOB column). The solution to this is to specific an SQL type on the mapping files, so as to force the generatiion of TEXT/CLOB fields in the generated database. An alternative is to look at any string defined as 4000 and re-assess theses lengths. Is 4000 always needed ? I suspect not, and if it is, might not sometimes 4001 or greater be needed ? One could probably get away with reducing many of these string lengths, but by makign them all CLOBs anyway, yo do not have to wory about ever blowing the current 4000 byte limit, and you solve the iSeries DB2 problem as well. PS as iSeries are not machines you tend to have lying around to test on, I can test any changes needed for the project.