SliTaz GNU/Linux official and community documentation wiki.
Translations of this page:

This is an old revision of the document!

SQLite is a lightweight SQL database and as such perfectly suitable for use with slitaz. Leightweight does however not imply that its functionality is also limited; rather the opposite!

To begin with, the program in all its aspects is extensively documented on: This leaves fairly little left to be documented elsewhere. If you have never worked with SQL before, this guide will provide sufficient information to get you started and to determine whether SQLite is the proper choice for your database.

Contrary to virtually all other SQL database solutions, you don't need a server to run SQlite. The database consists of a single file which is accessed via the sqlite command line tool or through a programming language like Perl or Python. Apart from the inherent simplicity, the big advantage of this approach is that it is VERY fast, even while running on low-end hardware. Backups are easy too; you just save the file holding the database to another location. These properties make SQLite probably the best choice for single user and embedded solutions. Small-scale CGI is another application which works very well with SQLite. All of this and more is described on:

What do you need to get started on Slitaz? -To begin with, you need to install the sqlite client package:

# tazpkg -gi sqlite 

This installs the sqlite client in your /usr/bin directory. The version offered with slitaz is a stable release but not the latest one available. SQLite is under active development and new versions appear on a regular basis. If you need a more recent version you may use the precompiled binary which is available on the download page. To do this, you can simply download the precompiled binary and save it in the /usr/bin/ folder, overwriting the file from the tazpkg installation if it exists.

The version of the SQLite client is only backwards compatible with the database file. You cannot access a database which was created -for example- using version with an older release of the client like 3.7.9. The opposite -a newer client opening a database created with a previous version- is generally possible. This can be relevant if you need to access a single database from different clients. Best practice is to use the same version of the client everywhere.

To run SQLite with Perl, one additional package must be installed; the perl-sqlite module:

# tazpkg -gi perl-dbd-sqlite 

Using SQLite with Perl, Python or any other language is documented extensively on various websites and describing it here would be out of scope as far as this document is concerned. The saying “Google is your friend” really applies in this case.

The sqlite client /usr/bin/sqlite3 allows you to do anything from the command line which also can be done using Perl, Python or any other language. You can print, update, add or delete records and manipulate columns and tables. Starting the program without any parameters or options returns a > prompt. You may enter sql commands terminated by the semcolon (;) as is normal in all sql dialects. Query's must contain a reference to the database file and the sql part must be between double quotes and terminated by a semicolon (;). One small example:

sqlite3 /home/tux/yourdatabase "select * from sqlite_master;"

This command prints the layout of the tables in the database. To create a new database, set the filename to whatever is deemed suitable. A new database is created if the file does not exist.

Please refer to for the commands to create tables and add columns to them. Its all pretty straightforward and virtually the same as with most other SQL versions. If you are completely new to SQL, you will have something of a learning curve but many things picked up here can be used with other SQL versions too. It's certainly worth it!

Copying or renaming the file containg the database is also trivial. To make a copy simply type:

$ cp /home/tux/yourdatabase /home/tux/mydatabase 

The filesize depends heavily on the type of database and its actual contents. The more data is entered, the larger the file becomes. Please note that the file does not shrink when a large amount of data is deleted. Instead, the empty space is preserved and re-used before the file starts to increase in size again. Something else to keep in mind is that the file permissions must be set correctly to be able read or write the database.

en/guides/database.1367005138.txt.gz · Last modified: 2013/04/26 21:38 by emgi