Issue #5424 has been updated by Daniel Crawl. Status changed from New to Resolved Target version changed from Unspecified to 2.5.0
HSQL updated to v2. ---------------------------------------- Bug #5424: see if it's worthwhile to upgrade hsql from 1.8 https://projects.ecoinformatics.org/ecoinfo/issues/5424#change-21925 * Author: Derik Barseghian * Status: Resolved * Priority: Normal * Assignee: Daniel Crawl * Category: provenance * Target version: 2.5.0 * Bugzilla-Id: 5424 ---------------------------------------- Currently hsql is at v2.2, but we're still using 1.8. There are a number of benefits to upgrading to 2.2. Dan and I discussed it and it seems worthwhile to test, esp to see if performance improves -- we have some really poor performance in some areas. E.g. the growingDegreeDays workflow with days set to 300 can take up to 13m to run with provenance turned on, but <10s with provenance turned off. And bug#5413 discusses how large run deletion from WRM can take way too long. I tried to upgrade my 1.8 provenance data to 2.2 today, but wasn't able to. I couldn't get a connection made to the db from 2.2. There are errors about the first ALTER line in the provenanceDB.script file: org.hsqldb.HsqlException: error in script file line: 49 invalid expression in CHECK or GENERATED clause in statement [ALTER TABLE WORKFLOW_EXEC ADD CONSTRAINT WORKFLOW_EXEC_WF_ID_FK FOREIGN KEY(WF_ID) REFERENCES WORKFLOW(ID) ON DELETE CASCADE] I spent some time manually hacking the script file, but wasn't able to figure out what's wrong here... -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: https://projects.ecoinformatics.org/ecoinfo/my/account
_______________________________________________ Kepler-dev mailing list [email protected] http://lists.nceas.ucsb.edu/kepler/mailman/listinfo/kepler-dev
