Bug 140268 - Adding jar for HSQLDB JDBC driver breaks embedded HSQLDB
Summary: Adding jar for HSQLDB JDBC driver breaks embedded HSQLDB
Status: RESOLVED DUPLICATE of bug 34411
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Base (show other bugs)
(earliest affected) release
Hardware: All All
: medium normal
Assignee: Not Assigned
Depends on:
Reported: 2021-02-08 16:24 UTC by michael
Modified: 2021-07-16 14:39 UTC (History)
4 users (show)

See Also:
Crash report or crash signature:
Regression By:


Note You need to log in before you can comment on or make changes to this bug.
Description michael 2021-02-08 16:24:03 UTC
In order to connect to an external HSQLDB database via JDBC (e.g. a DB running in server mode), I need to get a current HSQLDB JAR and add it to the classpath, as for any JDBC driver.

However, when I do that and open a DB which uses the embedded HSQLDB engine, I cannot access any tables, presumably due to a conflict between the two HSQL versions—one that is bundled with LO for the embedded DB, and the other I need for JDBC. If I need both use cases (external and embedded HSQLDB), I constantly have to adapt my configuration, and it is impossible to open two different kinds of DB side by side.

Granted, embedded HSQLDB is deprecated, but that doesn’t mean databases using that engine are going away overnight—migration may be complex and require a lot of manual intervention, so we’ll still need that support for quite a while.

However, I suppose the HSQLDB engine which ships with LO already includes a JDBC driver (it’s bundled into the jar, unless you have made some heavy modifications to it). So the solution would be to let the user to select that. Users would be constrained to that particular version of HSQLDB, but that should not be an issue when connecting to an instance running in server mode (and that could be used as a workaround to access an external HSQLDB file which is not compatible with the bundled HSQL version).
Comment 1 Alex Thurgood 2021-02-09 07:16:22 UTC

This problem has been around a very long time on macOS.

Could you just confirm which OS you are using so that I can check whether or not it is a duplicate of a previously filed bug report ?
Comment 2 Alex Thurgood 2021-02-09 07:21:13 UTC
Sounds like a DUP of bug 34411

The problem might be dependent both on your OS and the version of hsqldb.jar that you want to use.
Comment 3 Alex Thurgood 2021-02-09 07:23:46 UTC
See also bug 139538 for a suggested workaround on Linux.
Comment 4 michael 2021-02-09 08:36:35 UTC
In this case the platform was Windows 10. The HSQLDB jar was version 2.5.1.
Comment 5 QA Administrators 2021-02-10 04:12:41 UTC Comment hidden (obsolete)
Comment 6 Robert Großkopf 2021-07-16 14:39:22 UTC
This is indeed bug 34411.
Please try the macro described here:

I will set this one as duplicate of bug 34411. Feel free to reopen, if you think it's wrong.

*** This bug has been marked as a duplicate of bug 34411 ***