SQLite

3.5.7

Released on 17 Mar 2008
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.7 Changelog
  • Fix a bug (ticket #2927) in the register allocation forcompound selects - introduced by the new VM code in version 3.5.5.
  • ALTER TABLE uses double-quotes instead of single-quotes for quotingfilenames.
  • Use the WHERE clause to reduce the size of a materialized VIEW inan UPDATE or DELETE statement. (Optimization)
  • Do not apply the flattening optimization if the outer query is anaggregate and the inner query contains ORDER BY. (Ticket #2943)
  • Additional OS/2 updates
  • Added an experimental power-of-two, first-fit memory allocator.
  • Remove all instances of sprintf() from the code
  • Accept "Z" as the zulu timezone at the end of date strings
  • Fix a bug in the LIKE optimizer that occurs when the last characterbefore the first wildcard is an upper-case "Z"
  • Added the "bitvec" object for keeping track of which pages havebeen journalled. Improves speed and reduces memory consumption, especiallyfor large database files.
  • Get the SQLITE_ENABLE_LOCKING_STYLE macro working again on Mac OS X.
  • Store the statement journal in the temporary file directory instead ofcollocated with the database file.
  • Many improvements and cleanups to the configure script