Skip to content

Switch from Derby to HSQLDB; re-implement DatabaseUtils, el al.

Latest

Choose a tag to compare

@sbabcoc sbabcoc released this 17 Feb 15:09
· 1 commit to master since this release

In this release, I switched from Apache Derby to HSQLDB (HyperSQL DataBase). HSQLDB is much more strict in its compliance with SQL standards, which exposed the non-standard Derby behaviors I'd been relying on. To eliminate reliance on these features and resolve code factoring issues, I re-implemented significant portions of DatabaseUtils and its component classes.

  • Handling of variable argument lists now uses standard SQL arrays instead of Derby's VARARGS extension. This means that the number of arguments passed to stored procedures always matches the length of the parameter type array. This holds true even if NO variable-length arguments are specified. In this case, an empty array will be specified.
  • Handling of stored procedures that return multiple result sets has been corrected by providing an iterator to traverse the stream of results.
  • I removed the OUT_VARARGS stored procedure and its associated test, as this relied on Derby's non-standard VARARGS extension.

I upgraded to the latest Maven plug-ins. I also added some missing JavaDoc.