Libre Base Errors

Hi
Libre Office
Version: 4.2.7.2
Build ID: 420m0(Build:2)
English
Base

DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=14.04
DISTRIB_CODENAME=trusty
DISTRIB_DESCRIPTION=“Ubuntu 14.04.1 LTS”

I am new to Linux and therefore Libre Base

I should be grateful if you could give me an answer to my question before I waste any more time…

I have been using Base to provide a database for my paintings via a simple form. I recorded 200 records and then added the facility to include a photograph .jpg file and this is when the gremlins started to appear.

It constantly issues error messages when adding data and causes me to endlessly loose work as it has failed to write to the table from a form for no obvious reason I can see, sometimes I can add a new data or several set/records on the form OK and then it will fail with the error message as follows where the Table1 is my Table

S1000 General error java.lang.NullPointerException in statement [update “Table1” SET “Photo”=? Where ID=?}

Is is a know issue that it is unstable ? In addition I set auto save and backup yet fail to find them anywhere.

Any help will be very appreciated and I am ok to provide my database for analysis if required by genuine helper

cheers
alan

Yes, it is a known issue that when the embedded database becomes large, e.g. when storing images as binary stream data, then it can become unstable and lead to data loss.

Autosave doesn’t work properly, it currently produces 0 byte files.

After suffering from severe data loss myself, I was told that the default embedded database is pretty much unusable (people from the dev community might want to comment on whether that is true, and if so, why users are still lured into using it). The recommended approach seems to be to use a so-called “split database”. There is a nice explanation/howto and ready-to-use script at [Wizard] Create a new 'split' HSQL 2.x database (View topic) • Apache OpenOffice Community Forum.

MySQL / MariaDB is a good backend too.

@doug: Any drop-in replacement fork of MySQL is better than regular MySQL. We’re using Percona Server (the only problem of Percona Server is it’s Linux-only), but will migrate to MariaDB in near future.Funny, I’ve never had issues with LO’s integrated db system, as little as I’ve used it.

@rautamiekka: MySQL still has the best documentation and JDBC connector, mix and match with MariaDB core. Occasionally wish I went with PostgreSQL instead. Need higher degree of reliability and interoperatibility than LO integrated HSQLDB, although the more I know about the native LO solution, the more ok it sounds.