[jbpm-issues] [JBoss JIRA] Resolved: (JBPM-1843) Revert to jbpm-3.2.2 schema and provide a defined migration path

[ https://jira.jboss.org/jira/browse/JBPM-1843?page=com.atlassian.jira.plug... ] Thomas Diesler resolved JBPM-1843. ---------------------------------- Resolution: Done We don't need to revert the schema. The current 3.3.0 schema is indeed backward compatible. Here is the proof #1 On Sybase I created a jbpm322 database, which I loaded with the jbpm-3.2.2 schema #2 I resurrected the SchemaUpdate tool (JBPM-1823) to generate a jbpm-3.3.0 schema update script (this only adds one column) #3 I created a jbpmcomp database, which I loaded with the jbpm-3.2.2 schema and the jbpm-3.3.0 update script #4 I point the QA matrix at the jbpmcomp database The Matrix runs successful http://jbpm.dyndns.org:8280/hudson/job/jBPM3-Matrix/11/ That mean that customers can upgrade to jbpm-3.3.0 without having to change the datatype from varchar(4000) to text. Hibernate + the Sybase jTDS driver will compensate for the difference in SQL data type and work with both schemas. -- 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