SQLite is an embedded relational database engine written in C that provides SQL functionality without requiring a separate server process. This repository serves as the official Git mirror of the SQLite source tree, containing the complete source code dating back to May 29, 2000. The primary source code resides in the src/ directory, which contains the core SQLite engine along with testing code and TCL interface bindings. The repository is classified across multiple domains including Database, Relational, Embedded, SQL, Transactional, Serverless, Storage, ACID, File-based, and Lightweight, reflecting its design as a self-contained, zero-configuration database system suitable for embedded applications.
The repository structure is organized into several key directories. The src/ directory houses the primary SQLite core implementation, while the test/ directory contains TCL scripts and C code modules for comprehensive testing through an augmented TCL interpreter called testfixture. The tool/ directory includes the Lemon parser generator and various TCL scripts that build machine-generated code and perform transformations on source files, such as the mksqlite3h.tcl script that generates the sqlite3.h interface header. The ext/ directory contains optional extensions including FTS5 for full-text search, RTREE for spatial indexing, and various miscellaneous single-file extensions found in ext/misc/.
SQLite's source code management uses Fossil, a distributed version control system specifically designed to support SQLite development. The official Fossil repository serves as the authoritative source, while this GitHub repository functions as a mirror. The README emphasizes that official check-in names are found in the manifest.uuid file and in footers of check-in comments, distinguishing them from Git-generated names. Users can obtain source code through tarballs, ZIP archives, or direct Fossil access, with options to check out specific versions, releases, or trunk versions from particular dates.
The project supports compilation on both Unix-like systems and Windows using MSVC. On Unix systems, the build process involves running a configure script generated with autosetup, followed by make commands to produce deliverables like sqlite3.c (the amalgamation), the sqlite3 command-line tool, sqldiff for comparing databases, and sqlite3_analyzer for database inspection. Windows builds use either a make.bat wrapper or direct nmake commands with Makefile.msc. The build system supports optional compile-time configuration through the OPTIONS parameter, allowing developers to omit deprecated features or customize the build. Testing requires TCL development libraries and can range from development tests to full release tests that may require additional tools like valgrind.
SQLite's source code is released into the public domain, which influences the project's contribution policy. The repository explicitly does not accept pull requests because accepting external contributions could introduce copyright claims that would compromise the public domain status of the codebase. The project directs users to the SQLite Forum for questions and discussions, with a separate bugs forum for issue reporting and a private email option for security-related concerns. This governance structure reflects SQLite's focus on maintaining code quality and legal clarity while remaining freely available for any use.
