A Change Summary is available on this website. You can also access a detailed change history, view open bugs, or report new bugs at the CVS server.
Complete source code and precompiled binaries for the latest release are available for download on this site. You can also obtain the latest changes by anonymous CVS access:
When prompted for a password, enter "anonymous".cvs -d :pserver:firstname.lastname@example.org:/home/cvs/sqlite login cvs -d :pserver:email@example.com:/home/cvs/sqlite checkout sqlite
Note that the CVS server is located on a cable modem with a dynamic IP address. The IP address changes every 3 or 4 months. After an IP address change occurs it usually takes a day or two for the new DNS information to propagate. So if you have trouble accessing the CVS server, it could be because the IP address has recently changed. Try again in a few days.
Whenever either of the first two digits in the version number for SQLite change, it means that the underlying file format has changed. Usually these changes are backwards compatible. See formatchng.html for additional information.
Beginning with version 2.6.0, the SQLite database file format changed in an incompatible way. If you open a database file from version 2.5.6 or earlier with version 2.6.0 or later of the library, then the file format will be converted automatically. This is an irreversible operation. Once the conversion occurs, you will no longer be able to access the database file from older versions of the library. If the database is large, the conversion might take some time. (Allow 1 to 2 seconds per megabyte of database under Linux.) If the database is read-only, the conversion cannot occur and the attempt to open the database will fail. It is suggested that you make backup copies of older database files before attempting to open them with version 2.6.0 or later of the library.
The following documentation is currently available:
The SQLite source code is 30% comment. These comments are another important source of information.
Click to subscribe to sqlite
A mailing list has been set up on yahooGroups for discussion of SQLite design issues or for asking questions about SQLite.
If you would like professional support for SQLite or if you want custom modifications to SQLite preformed by the original author, these services are available for a modest fee. For additional information contact:
D. Richard Hipp
Hwaci - Applied Software Research
To build sqlite under Unix, just unwrap the tarball, create a separate build directory, run configure from the build directory and then type "make". For example:
$ tar xzf sqlite.tar.gz Unpacks into directory named "sqlite" $ mkdir bld Create a separate build directory $ cd bld $ ../sqlite/configure $ make Builds "sqlite" and "libsqlite.a" $ make test Optional: run regression tests
If you prefer, you can also build by making whatever modifications you desire to the file "Makefile.linux-gcc" and then executing that makefile. Tha latter method is used for all official development and testing of SQLite and for building the precompiled binaries found on this website. Windows binaries are generated by cross-compiling from Linux using MinGW
For information bindings of SQLite to other programming languages (Perl, Python, Ruby, PHP, etc.) and for a list of programs currently using SQLite, visit the Wiki documentation at: