Use SQLite 2.8.x to read single file SQLite databases under Linux (and later Windows).
On Linux, install the SQLite binary package suitable for your distro. The minimum SQLite version required is 2.8.13
Install OpenOffice.org 1.1 or newer.
Download the binary version of the driver.
sqlite-sdbc-driver-0.1.0.zip
Copy the zip file in OpenOffice1.1/user/uno_packages
folder (Note: USE the zip file as a whole, DO NOT extract it). Open
up a shell and switch to the OpenOffice1.1/program directory and
start the pkgchk tool. On success, no output is given. Alternatively,
you can install the driver for all users of a OpenOffice.org network
installation by placing the file into the OpenOffice1.1/share/uno_packages
and starting pkgchk --shared You can uninstall the package by deleting
the file in the uno_packages directory and starting pkgchk again.
You can now add a datasource via the common Tools/Data Sources dialog. Click on new datasource and select sqlite from the Database type combobox. Then put the file name of your SQLite database right after the sqlite: into the URL input field.
Format: sdbc:sqlite:sqlite_database_filename
The driver supports reading and writing SQLite 2 databases. It has the following limitations:
It uses the encoding of the SQLite engine. Depending on how SQLite was generated, this is ISO 8859-1 or UTF-8.
The data types supported for now are INTEGER and VARCHAR. In result sets, INTEGER is only reported for "INTEGER PRIMARY KEY" fields, i.e. SQLite's auto incrementing columns. All other columns are VARCHARs.
It is possible to create new SQLite tables from OpenOffice.org's table designer. However, creating/deleting indexes may fail due to bugs in SQLite's SQL parser or OpenOffice.org's SQL dialect.
The driver may contain memory leaks and bugs which can crash OpenOffice.org
Linux: Fetch the source code
and unpack it in .../connectivity/source/drivers. Setup your OOo environment
for building, then goto the .../connectivity/source/drivers/sqlite directory
and type dmake. The source code expects the SQLite header files and libraries
in standard places (/usr/include and /usr/lib)
Building on Windows should be possible but was not tested so far.
The driver has been implemented based on the MDB driver by Christian Werner(chw@openoffice.org)