SQLite

3.5.3

Released on 27 Nov 2007
Project description.

SQLite is an in-process library that implements a self-contained, serverless, zero-configuration, transactional SQL database engine. The code for SQLite is in the public domain and is thus free for use for any purpose, commercial or private. SQLite is the most widely deployed database in the world with more applications than we can count, including several high-profile projects.

SQLite is an embedded SQL database engine. Unlike most other SQL databases, SQLite does not have a separate server process. SQLite reads and writes directly to ordinary disk files. A complete SQL database with multiple tables, indices, triggers, and views, is contained in a single disk file. The database file format is cross-platform - you can freely copy a database between 32-bit and 64-bit systems or between big-endian and little-endian architectures. These features make SQLite a popular choice as an Application File Format.

SQLite 3.5.3 Changelog
  • Move website and documentation files out of the source tree intoa separate CM system.
  • Fix a long-standing bug in INSERT INTO ... SELECT ... statementswhere the SELECT is compound.
  • Fix a long-standing bug in RAISE(IGNORE) as used in BEFORE triggers.
  • Fixed the operator precedence for the ~ operator.
  • On Win32, do not return an error when attempting to delete a filethat does not exist.
  • Allow collating sequence names to be quoted.
  • Modify the TCL interface to use sqlite3_prepare_v2().
  • Fix multiple bugs that can occur following a malloc() failure.
  • sqlite3_step() returns SQLITE_MISUSE instead of crashing whencalled with a NULL parameter.
  • FTS3 now uses the SQLite memory allocator exclusively. TheFTS3 amalgamation can now be appended to the SQLite amalgamation togenerate a super-amalgamation containing both.
  • The DISTINCT keyword now will sometimes use an INDEX if anappropriate index is available and the optimizer thinks its usemight be advantageous.