Date: prev next · Thread: first prev next last
2012 Archives by date, by thread · List index

Am 18.03.2012 08:56, Mark Stanton wrote:
I think the point Mark was making was to switch away from using the
embedded back-end to pretty much any external one.  Which is what
you often suggest too.

Yes indeed.
Can HSQLDB be used as an external engine?  I thought not, which is why I didn't
include it.

Mark Stanton
One small step for mankind...
Download the latest version.
Put it somewhere in your libraries (no installation required).
Point your office Java to the extracted hsqldb.jar.
Extract ./database/ from your embedded database somewhere to your files.
Rename your database files with a common "dbname." prefix.
Connect a new Base document using JDBC with an URL like this one (refer to the downloaded documentation in your libs):
Copy over the queries, forms and reports from your embedded thing.

You get the latest version of a full featured HSQLDB without restrictions, many more functions, the access control and safety you would expect from a database application.
You can write a configuration file to run a server for concurrent access.

- Embedded HSQL requires another Java config. I use OOo for embedded and LibO 3.3.4 for "normal" access. - Base can not handle user defined row filters with HSQLDB2. I use my own "power filters" anyway.

For unsubscribe instructions e-mail to:
Posting guidelines + more:
List archive:
All messages sent to this list will be publicly archived and cannot be deleted


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.