[SAK-28053] Remove support for HSQLDB (1.8) Created: 05-Nov-2014  Updated: 22-Jan-2018

Status: OPEN
Project: Sakai
Component/s: Release Management
Affects Version/s: 11.0
Fix Version/s: None

Type: Task Priority: Major
Reporter: Matthew Jones Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: bcreview, triagecritical
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
relates to SAK-27882 First LTI tool installed can not upda... RESOLVED
relates to SAK-27802 Forums does not work on HSQLDB CLOSED
relates to SAK-38715 Tomcat pooling doesn't work with HSQLDB CLOSED
relates to SAK-39652 Upgrade to Hibernate 4.3.x RESOLVED
relates to SAK-23674 Replace the use of HSQLDB with H2 usi... OPEN


HSQLDB is no longer going to be supported in Sakai 11.

See the Strawman Proposal: https://confluence.sakaiproject.org/display/REL/Sakai+11+straw+man

So a few things need to be done:

  • It should no longer include the jar(s) by default
  • HSQLDB scripts should be removed from kernel and other places that use it (because they won't work anyway if we ever do upgrade)
  • Jiras that involve a problem specific to HSQLDB should be closed as "Won't Fix"
  • New 11 nightly instances won't be running HSQLDB (Already planned)
  • The Sakai Demo needs to include a readme and documentation for how to startup Sakai on MySQL

After this is done, the unit tests will still run on HSQLDB, but ideally these will be updated over time. So ensure the unit tests aren't broken.

Comment by Matthew Jones [ 13-Jun-2017 ]

HSQLDB for tests was updated in KNL-945 to 2.3.4. It's possible Sakai may startup with a little work on this newer hsqldb, or it might take a lot of changes. But we wouldn't want to remove anything that breaks tests.

Comment by Charles Severance [ 06-Sep-2017 ]

Can we start removing hsql support for non-unit test stuff?

Comment by Matthew Jones [ 06-Sep-2017 ]

Yeah I'm just lowering this and unassigning myself because it's not priority for me to remove this stuff.

Generated at Wed Feb 19 19:17:00 CST 2020 using Jira 8.0.3#800011-sha1:073e8b433c2c0e389c609c14a045ffa7abaca10d.