SQLite and PostgreSQL support with JDBI and HikariCP

[matteotrubini]

Work is in progress to add SQLite support as a future-proof replacement for Apache Derby, which was officially retired by the Apache Software Foundation.
Ref: https://db.apache.org/derby/derby_downloads.html#Derby+Retired

The implementation is essentially complete and passes all build tests. I'm waiting for existing PRs to merge before publishing the code, to proactively handle any potential rebase conflicts.

[bicodrex]

I really like this, @matteotrubini SQLite as a replacement for Derby makes a lot of sense, especially since Derby is retired.

I think this goes very well together with the import feature I was thinking about [#10].

A couple of points I wanted to discuss:

• It would be great to make SQLite the default option in the dropdown for new installations.
• For cross-OS safety, maybe the GUI could let users choose a file path if they use SQLite.
• I’d suggest keeping Derby support for a while to allow existing databases to still work.

Overall, this looks solid and lays a good foundation for smoother migrations and future-proofing.
What do you think about these points?

[matteotrubini]

• It would be great to make SQLite the default option in the dropdown for new installations.

I agree.

• For cross-OS safety, maybe the GUI could let users choose a file path if they use SQLite.

It should use the same location where the logs are saved. Whether it’s relative to the executed JAR, the home directory, or elsewhere, everything should stay together.

• I’d suggest keeping Derby support for a while to allow existing databases to still work.

Of course. Before its final deprecation, the migration to another supported database should be properly managed.