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

Hi :)
A quick "back of an envelope" risk-analysis might suggest that
although the effects can be fairly devastating the likelihood of that
occurring is fairly low so it might be acceptable.

It might be something like that which led Ian's "MySql expert" to say
it was fine only for proto-typing, or it might be that the expert
needs people to all move to MySql and has a sales-pitch against each
different type of other non-MySql program.  The argument against
MariaDb might be that it doesn't work on Macs.

The LO marketing team keep insisting on pretending that the internal
database is ok.  Most of the rest of us seem to have to pick up the
pieces when/if that goes wrong so we seem to generally advise people
to move to an external back-end asap (within reason).  However it's
very rare that people do run into the problem so maybe it is being
over-stated.  Plus, how hard can it be to back-up a single file!  On
the other hand the effects are TOO devastating and far beyond what
most of us on this list would find acceptable

Just to add 2 extra layers of complexity
1.  the internal (embedded) database 'back-end' is apparently likely
to be switched from Hsql to something else 'soon'.
2.  Hsql is a separate 3rd party project and it's possible to download
and install their latest version on 'your computer' (or server or
anything) and use that in much the same way you use any other external

Apparently the only reason the the internal back-end is sometimes
unstable is because Sun paid-devs insisted on locking in a now ancient
version and they heavily tweaked it.  Apparently this was fine "back
in the day" but nowadays means that the internal back-end is.  Also
apparently when the newer&untweaked versions of Hsql are being used as
an external back-end then it's quite excellent and very stable.

So i don't think it's really fair to blame Hsql.  It's be a bit like
saying that OOo 1.0 is a bit ancient and not great nowadays.

Regards from
Tom :)

On 7 February 2014 15:44, Jay Lozier <> wrote:

On 02/07/2014 10:29 AM, Lens Paul wrote:


This instability of HSQL is worrying when using the same database year
after year, e.g. an address or a bibliographic database.

For my part, all my data remain in separate external tables in dbf format,
linked to Base.

Reasons are:
- compatibility with many programmes and readability of old archives, even
in case of change of database program ;
- stability in the long run;
- format compatible with GIS software;
- when the tables are not merged in one file, the loss is limited when one
of the tables gets corrupted.

The main drawback is the impossibility to make a relational database.

In fact, the good integration of the office suite with a database was one
of the main reason's why I began to use OO in 2007 or 2008.

To my great satisfaction indeed: it works very well, except for two
instances, several years ago, where the dbf file got corrupted (luckily,
recovery from backups was easy).
Since then it works fine without any failure (except, rarely, for some
data in memo fields, which can lose the right connection with other data
(dbt file connection to dbf file)).

Nevertheless, the impossibility of making relations between tables is
rather frustrating.
One solution is to migrate to a mySQL/Base or preferably Postgresql
(because of PostGIS). It's my intention but I fear to waste a lot of time in

What is the best combination for a single user, relational database,
stable in the long run, using Base as the front end?

Paul Lens


PostgreSQL and MySQL/MariaDB are good alternatives. MariaDB is a fork of
MySQL and many Linux distros install it instead of MySQL. Both can be used
as a single user database. IMHO MariaDB is easier to use in a single user
environment. With both you can use Base or database specific GUI (pgAdmin,
MySQL Workbench).

If the data can be exported to csv files migrating should not be difficult,
only time consuming.


Le 7/02/2014 15:07, Ian Whitfield a écrit :

Sorry All

I'm running PClinuxOS (latest) and LO and MySQL 5.1.55

A MySQL 'expert' was telling me recently that HSQL is only meant to be a
prototyping utility and should *NEVER* be used for any "proper" work - -

I can confirm that when it crashes it takes everything with it so you
have to backup every time you make change. This is what forced me to MySQL.

Thanks again

Jay Lozier

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

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.