Base with HSQLDB 2.7.4

[runningchark]

Hi all, looking at getting back into LO Base things. I had previously been using DACM’s split macro with a newer version of HSQL which worked very well. For my new setups, are there any concerns with using the most recent version of HSQLDB with Base? Whether with the macro or as a HSQL server.

Going back to HSQL from my PostgreSQL things so I know about the various bugs that still exist, but just wondering what the community is running. I also see firebird seems to still be “experimental”. Any success stories there?

Thanks.

[Wanderer]

@runningchark

Whether with the macro

IMHO the newer HSQLDB lost the ability to read the old 1.8-databases, so you would need an intermediate version (I think 2.4), but the expert on this is @Villeroy

@runningchark

as a HSQL server

Here you will have the same “problem” as with postgres etc. If Base does not know the functions etc you have to use SQL-direct mode.

@runningchark

firebird seems to still be “experimental”. Any success stories there?

Yes, it is set again as experimental, but I don’t think this reflects on the database, but on “seamless integration” in Base. Maybe check the german guide for Base and as an example the Xrechnung also by @RobertG

Datenbanken

[Villeroy]

@runningchark

I had previously been using DACM’s split macro with a newer version of HSQL which worked very well.

So you have a version 2.x up and running. Shut down LibreOffice and any other connection to that database, replace the hsqldb.jar driver and restart.

What’s wrong with LibreOffice and PostgreSQL?

[runningchark]

Thanks! I set up an HSQLDB server yesterday & rewrote the macro access code to work for my needs and it seems to work well with 2.7.4.
& as much as I love postgresql, I have a need for a more portable db. Even with hsql running as a server it can still be started and stopped without needing to install anything on my computer and with server mode I can get to it concurrently with dbeaver, etc.

Nothing wrong with postgresql itself. Outside of the Base/Writer form design crashes the other nagging bug with the postgresql sdbc driver was that identity columns don’t return their ID when you insert a new row to the base GUI. So subsequent subforms don’t get the correct ID unless you refresh the parent. I don’t recall if it worked with the JDBC driver but doesn’t matter now, this will work well enough.

[RobertG]

@runningchark

identity columns don’t return their ID

This is 60643 – EDITING - postgresql-SDBC GUI autoincrement setting not saved in Table Design mode
Workaround by using Tools → SQL:

CREATE TABLE "public"."Test" ("ID" SERIAL PRIMARY KEY);

This would create an auto increment key, which will work well - also with subforms.
.
But: There are other (little) bugs for PostgreSQL. Hope they will be fixed by the new developer for Base (Join the LibreOffice Team as a Paid Developer focusing on the Base database application, preferably full-time, remote (m/f/d) - TDF Community Blog), who joined to TDF at 2026-04-01.