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

Am 01.03.2015 um 22:01 schrieb Jay Lozier:

What is the current backend for Base?

I remember at one time is HSQL 1.8 but one could install a later


When you create a new database document without Java support, then you
get a directory of flat dBase files handled by LibreOffice's
insufficient SDBC driver for dBase.

With Java support it will be an embedded HSQL 1.8 database which is more
a caricature of a database because it is slow, unsafe and insecure. The
problem is _not_ HSQL. The problem is the way how the backend is wrapped
into the zip archive which constitutes the "Base document".
It is easy enough to convert an embedded HSQLDB to a normal (external)
database and use it with a recent and more capable version of HSQL.
Current version is 2.3. On the OpenOffice user forum you can find
several tutorials, scripts and macros. But you can also use HSQL 1.8
with an external database if that version fits your needs. Just do not
use a self-contained database in a single file for anything but
educational stuff, demos or small projects for a single user on a local
machine with a sound backup strategy.

Otherwise you can connect a Base document to any database you have a
driver for (ADO, ODBC, JDBC).

To unsubscribe 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.