[ https://jira.jboss.org/jira/browse/JBPM-2057?page=com.atlassian.jira.plug... ] Thomas Diesler commented on JBPM-2057: -------------------------------------- I'm rolling back this fix, which effectively restores the original jbpm322 schema except for the JBPM-1755 related additional column. Looking at the email exchange below, it seems that Goldman Sachs does not strictly require a switch to type="text". I propose that we work directly with them to find out what they actually need. This issue is moved to 3.2.x ------------------------------------------ Also, to migrate, can not we just manually convert the data from <4000> to <text> columns? -----Original Message----- From: Xu, Xiangdong Sent: Friday, February 20, 2009 3:20 PM To: Xu, Xiangdong; 'Burr Sutter' Cc: 'Thomas Diesler'; 'Scott Sajer' Subject: RE: https://jira.jboss.org/jira/browse/JBPM-2057 Hi, just read the case and Thomas' comments. Due to migration issue. Thomas suggested a adding additional columns. Would that be the approach for other varchar(4000) columns? Does it completely solve the migration problem? -----Original Message----- From: Xu, Xiangdong Sent: Friday, February 20, 2009 11:00 AM To: 'Burr Sutter' Cc: Thomas Diesler; Scott Sajer Subject: RE: https://jira.jboss.org/jira/browse/JBPM-2057 Burr, thanks for getting back to me. Just to be clear that we have not seen truncation so far. We only see the warning message from Sybase since the page size of our Sybase server is 2k which could potentially cause truncation if the object size is larger than 2k. My questions is should we go with CLOB just to be safe? If we go CLOB, what is the related change has to be made? Thanks -xiangdong -----Original Message----- From: Burr Sutter [mailto:bsutter@redhat.com] Sent: Friday, February 20, 2009 7:51 AM To: Xu, Xiangdong Cc: Thomas Diesler; Scott Sajer Subject: https://jira.jboss.org/jira/browse/JBPM-2057 Xiangdong, We are working on a solution to address jBPM-2057 - truncating data into varchar(4000) columns. Thomas Diesler on our team is researching how we could accomplish this adjustment and has made some comments on the jira task. Our goal is to make a database portable solution and we have to be concerned about jBPM production databases as well. Can you tell us which columns are specifically the problem for your usage scenarios? Thomas may have some questions for you and your team as well. Thank you, Burr -- 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