Project

General

Profile

Bug #5424

see if it's worthwhile to upgrade hsql from 1.8

Added by Derik Barseghian almost 8 years ago. Updated about 4 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
provenance
Target version:
Start date:
06/15/2011
Due date:
% Done:

0%

Estimated time:
Bugzilla-Id:
5424

Description

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 REFERENCES WORKFLOW ON DELETE CASCADE]

I spent some time manually hacking the script file, but wasn't able to figure out what's wrong here...

History

#1 Updated by Derik Barseghian almost 8 years ago

see bug#5429 for more discussion

#2 Updated by Redmine Admin about 6 years ago

Original Bugzilla ID was 5424

#3 Updated by Daniel Crawl about 4 years ago

  • Target version changed from Unspecified to 2.5.0
  • Status changed from New to Resolved

HSQL updated to v2.

Also available in: Atom PDF