[jbpm-issues] [JBoss JIRA] Commented: (JBPM-2018) StringInstance hbm configuration column length of 4000

[ https://jira.jboss.org/jira/browse/JBPM-2018?page=com.atlassian.jira.plug... ] Thomas Diesler commented on JBPM-2018: -------------------------------------- Alejandro says: It was because of a request from Goldman Sachs: https://jira.jboss.org/jira/browse/JBPM-701 Every mapping of a String field with length="4000" was replaced with type="text". The complete list of differences was compiled by Thomas in https://jira.jboss.org/jira/browse/JBPM-1849 Back at the time we released 3.3.0 we discussed the consequences and our options. Either (a) rollback those changes or (b) verify they had no impact on existing database schemas. Thomas verified the jTDS driver transparently handled the difference between varchar(4000) and text, as per the comment in https://jira.jboss.org/jira/browse/JBPM-1849 I verified his findings on my local Sybase installation as well. If required, this verification can be repeated for each supported database. There is an issue which I just spotted and will correct immediately. https://jira.jboss.org/jira/browse/JBPM-2017 -- 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