SQLiteOOo logo Documentation

Ce document en français.

The use of this software subjects you to our Terms Of Use.

version 1.2.3

Introduction:

SQLiteOOo is part of a Suite of LibreOffice and/or OpenOffice extensions allowing to offer you innovative services in these office suites.

This extension allows you to use SQLite JDBC database in embedded mode, making the database portable (a single odb file).
It allows you to take advantage of the ACID properties of the underlying SQLite database.

Being free software I encourage you:

In short, to participate in the development of this extension.
Because it is together that we can make Free Software smarter.


Requirement:

Due to issue #156471 and following PR#154989, the SQLiteOOo extension requires LibreOffice version 24.2.x minimum to work.

The SQLiteOOo extension uses the jdbcDriverOOo extension to work.
It must therefore meet the requirement of the jdbcDriverOOo extension.

If you are using LibreOffice on Linux and LibreOffice was installed with the package manager, Your Python packages may be system-provided and outdated. The extension’s logging will allow you to check if this is the case. It is accessible via the menu: Tools -> Options -> LibreOffice Base -> Embedded SQLite driver -> View log -> System Info and requires restarting LibreOffice after activation.
If outdated packages appear, you can update them with the command:
pip install --upgrade <package-name>

For more information see: What has been done for version 1.1.0.


Installation:

It seems important that the file was not renamed when it was downloaded.
If necessary, rename it before installing it.

Restart LibreOffice after installation.
Be careful, restarting LibreOffice may not be enough.

After restarting LibreOffice, you can ensure that the extension and its driver are correctly installed by checking that the io.github.prrvchr.SQLiteOOo.Driver driver is listed in the Connection Pool, accessible via the menu: Tools -> Options -> LibreOffice Base -> Connections. It is not necessary to enable the connection pool.

If the driver is not listed, the reason for the driver failure can be found in the extension’s logging. This log is accessible via the menu: Tools -> Options -> LibreOffice Base -> Embedded SQLite Driver -> Logging Options.
The SQLiteLogger logging must first be enabled and then LibreOffice restarted to get the error message in the log.

Remember to first update the version of the Java JRE or JDK installed on your computer, this extension need the new version of jdbcDriverOOo that requires Java version 17 or later instead of Java 11 previously.


Use:

How to create a new database:

In LibreOffice / OpenOffice go to File -> New -> Database…:

SQLiteOOo screenshot 1

In step: Select database:

SQLiteOOo screenshot 2

In step: Save and proceed:

SQLiteOOo screenshot 3

Have fun…


How does it work:

SQLiteOOo is an com.sun.star.sdbc.Driver UNO service written in Python.
It is an overlay to the jdbcDriverOOo extension allowing to store the SQLite database in an odb file (which is, in fact, a compressed file).

Its operation is quite basic, namely:

The main purpose of this mode of operation is to take advantage of the ACID characteristics of the underlying database in the event of an abnormal closure of LibreOffice. On the other hand, the function: file -> Save has no effect on the underlying database. Only closing the odb file or saving it under a different name (File -> Save As) will save the database in the odb file.


How to build the extension:

Normally, the extension is created with Eclipse for Java and LOEclipse. To work around Eclipse, I modified LOEclipse to allow the extension to be created with Apache Ant.
To create the HyperSQLOOo extension with the help of Apache Ant, you need to:


Has been tested with:

I encourage you in case of problem :confused:
to create an issue
I will try to solve it :smile:


Historical:

What has been done for version 1.0.0:

What has been done for version 1.0.1:

What has been done for version 1.0.2:

What has been done for version 1.1.0:

What has been done for version 1.1.1:

What has been done for version 1.1.2:

What has been done for version 1.1.3:

What has been done for version 1.1.4:

What has been done for version 1.1.5:

What has been done for version 1.2.0:

What has been done for version 1.2.1:

What has been done for version 1.2.2:

What has been done for version 1.2.3:

What has been done for version 1.3.0:

What remains to be done for version 1.3.0: