Jump to content

SQLite: Difference between revisions

From Wikipedia, the free encyclopedia
Content deleted Content added
Adding sqlite3 screenshot
Citation bot (talk | contribs)
Added chapter-url. Removed or converted URL. | Use this bot. Report bugs. | Suggested by Whoop whoop pull up | Category:SQLite | #UCB_Category 1/4
 
(42 intermediate revisions by 33 users not shown)
Line 18: Line 18:
| license = [[Public domain]]<ref name="license">{{cite web
| license = [[Public domain]]<ref name="license">{{cite web
| url = https://www.sqlite.org/copyright.html
| url = https://www.sqlite.org/copyright.html
| title = SQLite Copyright
| title = SQLite Copyright
| publisher = sqlite.org
| publisher = sqlite.org
| access-date = May 17, 2010}}</ref>
| access-date = May 17, 2010
| archive-date = October 10, 2023
| archive-url = https://web.archive.org/web/20231010232204/https://www.sqlite.org/copyright.html
| url-status = live
}}</ref>
| website = {{Official URL}}
| website = {{Official URL}}
}}
}}
Line 30: Line 34:
| _nomimecode = yes
| _nomimecode = yes
| mime = <code>application/vnd.sqlite3</code><ref>{{cite web
| mime = <code>application/vnd.sqlite3</code><ref>{{cite web
| url = https://www.iana.org/assignments/media-types/application/vnd.sqlite3
|url = https://www.iana.org/assignments/media-types/application/vnd.sqlite3
| title = SQLite database file format media type at IANA
|title = SQLite database file format media type at IANA
| website = [[Internet Assigned Numbers Authority]]
|website = [[Internet Assigned Numbers Authority]]
| publisher = [[Internet Assigned Numbers Authority|IANA]]
|publisher = [[Internet Assigned Numbers Authority|IANA]]
| access-date = 2019-03-08}}</ref>
|access-date = 2019-03-08
|archive-date = 2022-11-09
|archive-url = https://web.archive.org/web/20221109175151/https://www.iana.org/assignments/media-types/application/vnd.sqlite3
|url-status = live
}}</ref>
| type code =
| type code =
| uniform type =
| uniform type =
Line 47: Line 55:
}}
}}


'''SQLite''' ({{IPAc-en|ˌ|ɛ|s|ˌ|k|juː|ˌ|ɛ|l|ˈ|aɪ|t}},<ref>{{cite episode |series=The Changelog |number=201 |title=Why SQLite succeeded as a database — Richard Hipp, creator of SQLite |time=00:17:25 |url=https://changelog.com/podcast/201 |quote=How do I pronounce the name of the product? I say S-Q-L-ite, like a mineral.}}</ref><ref>{{cite video | people = [[D. Richard Hipp]] (presenter) | date = May 31, 2006 | title = An Introduction to SQLite | url = https://www.youtube.com/watch?v=f428dSRkTs4#t=1m14s | format = video<!-- HTML5 WebM video is available --> | publisher = Google Inc. | access-date =March 23, 2010 | time = 00:01:14 | quote = [...] ess-kju-ellite [...] }}</ref> {{IPAc-en|ˈ|s|iː|k|w|ə|,|l|aɪ|t}}<ref>{{cite video | people = [[D. Richard Hipp]] (presenter) | date = May 31, 2006 | title = An Introduction to SQLite | url = https://www.youtube.com/watch?v=f428dSRkTs4#t=48m15s | format = <!-- HTML5 WebM video is available --> | publisher = Google Inc. | access-date =March 23, 2010 | time = 00:48:15 | quote = [...] sequelite [...] }}</ref>) is a [[database engine]] written in the [[C Language|C programming language]]. It is not a standalone app; rather, it is a [[Library (computing)|library]] that [[Programmer|software developers]] embed in their [[Application software|apps]]. As such, it belongs to the family of [[embedded database]]s. It is the most widely deployed database engine, as it is used by several of the top [[Web browser|web browsers]], [[operating system]]s, [[Mobile phone|mobile phones]], and other [[embedded system]]s.<ref>{{cite web |url = https://sqlite.org/mostdeployed.html |title = Most Widely Deployed SQL Database Estimates |publisher = SQLite.org |access-date = May 11, 2011}}</ref>
'''SQLite''' ({{IPAc-en|ˌ|ɛ|s|ˌ|k|juː|ˌ|ɛ|l|ˈ|aɪ|t}},<ref>{{cite episode |series=The Changelog |number=201 |title=Why SQLite succeeded as a database — Richard Hipp, creator of SQLite |time=00:17:25 |url=https://changelog.com/podcast/201 |quote=How do I pronounce the name of the product? I say S-Q-L-ite, like a mineral. |access-date=2019-08-06 |archive-date=2022-07-07 |archive-url=https://web.archive.org/web/20220707033506/https://changelog.com/podcast/201 |url-status=live }}</ref><ref>{{cite video | people = [[D. Richard Hipp]] (presenter) | date = May 31, 2006 | title = An Introduction to SQLite | url = https://www.youtube.com/watch?v=f428dSRkTs4#t=1m14s | format = video<!-- HTML5 WebM video is available --> | publisher = Google Inc. | access-date =March 23, 2010 | time = 00:01:14 | quote = [...] ess-kju-ellite [...] }}</ref> {{IPAc-en|ˈ|s|iː|k|w|ə|,|l|aɪ|t}}<ref>{{cite video | people = [[D. Richard Hipp]] (presenter) | date = May 31, 2006 | title = An Introduction to SQLite | url = https://www.youtube.com/watch?v=f428dSRkTs4#t=48m15s | format = <!-- HTML5 WebM video is available --> | publisher = Google Inc. | access-date =March 23, 2010 | time = 00:48:15 | quote = [...] sequelite [...] }}</ref>) is a [[database engine]] written in the [[C Language|C programming language]]. It is not a standalone app; rather, it is a [[Library (computing)|library]] that [[Programmer|software developers]] embed in their [[Application software|apps]]. As such, it belongs to the family of [[embedded database]]s. It is the most widely deployed database engine, as it is used by several of the top [[Web browser|web browsers]], [[operating system]]s, [[Mobile phone|mobile phones]], and other [[embedded system]]s.<ref>{{cite web |url = https://sqlite.org/mostdeployed.html |title = Most Widely Deployed SQL Database Estimates |publisher = SQLite.org |access-date = May 11, 2011}}</ref>


Many [[Programming language|programming languages]] have [[Language binding|bindings]] to the SQLite library. It generally follows [[PostgreSQL]] syntax, but does not enforce [[type checking]] by default.<ref name="Owens 2006">{{cite book |last=Owens |first=Michael |year=2006 |chapter=Chapter 4: SQL |editor1-last=Gilmore |editor1-first=Jason |editor2-last=Thomas |editor2-first=Keir |editor2-link=Keir Thomas |title=The Definitive Guide to SQLite |url={{Google books|VsZ5bUh0XAkC|The Definitive Guide to SQLite|page=133|plainurl=yes}} |others=[[D. Richard Hipp]] (foreword), Preston Hagar (technical reviewer) |publisher=[[Apress]] |page=133 |isbn=978-1-59059-673-9 |access-date=30 December 2014}}</ref><ref>{{cite web | url=https://www.sqlite.org/stricttables.html | title=STRICT Tables }}</ref> This means that one can, for example, insert a string into a [[Column (database)|column]] defined as an integer.
Many [[Programming language|programming languages]] have [[Language binding|bindings]] to the SQLite library. It generally follows [[PostgreSQL]] syntax, but does not enforce [[type checking]] by default.<ref name="Owens 2006">{{cite book |last=Owens |first=Michael |year=2006 |chapter=Chapter 4: SQL |editor1-last=Gilmore |editor1-first=Jason |editor2-last=Thomas |editor2-first=Keir |editor2-link=Keir Thomas |title=The Definitive Guide to SQLite |chapter-url=https://books.google.com/books?id=VsZ5bUh0XAkC&pg=PA133 |others=[[D. Richard Hipp]] (foreword), Preston Hagar (technical reviewer) |publisher=[[Apress]] |page=133 |isbn=978-1-59059-673-9 |access-date=30 December 2014 |archive-date=24 November 2020 |archive-url=https://web.archive.org/web/20201124002058/https://books.google.com/books?id=VsZ5bUh0XAkC&pg=PA133 |url-status=live }}</ref><ref>{{cite web | url=https://www.sqlite.org/stricttables.html | title=STRICT Tables | access-date=2022-08-11 | archive-date=2022-08-07 | archive-url=https://web.archive.org/web/20220807204905/https://www.sqlite.org/stricttables.html | url-status=live }}</ref> This means that one can, for example, insert a string into a [[Column (database)|column]] defined as an integer.


==History==
==History==
[[D. Richard Hipp]] designed SQLite in the spring of 2000 while working for [[General Dynamics]] on contract with the [[United States Navy]].<ref name="Owens06">{{cite book |last=Owens |first=Michael |title=The Definitive Guide to SQLite |year=2006 |publisher=[[Apress]] |isbn=978-1-59059-673-9 |doi=10.1007/978-1-4302-0172-4_1}}</ref> Hipp was designing software used for a [[Damage control|damage-control]] system aboard guided-missile destroyers, which originally used [[HP-UX]] with an [[IBM Informix]] [[database]] back-end. SQLite began as a [[Tcl]] extension.<ref name=":0" />
[[D. Richard Hipp]] designed SQLite in the spring of 2000 while working for [[General Dynamics]] on contract with the [[United States Navy]].<ref name="Owens06">{{cite book |last=Owens |first=Michael |title=The Definitive Guide to SQLite |year=2006 |publisher=[[Apress]] |isbn=978-1-59059-673-9 |doi=10.1007/978-1-4302-0172-4_1}}</ref> Hipp was designing software used for a [[Damage control (maritime)|damage-control]] system aboard [[guided-missile destroyer]]s; the damage-control system originally used [[HP-UX]] with an [[IBM Informix]] [[database]] back-end. SQLite began as a [[Tcl]] extension.<ref name=":0" />


In August 2000, version 1.0 of SQLite was released, with storage based on [[gdbm]] (GNU Database Manager). In September 2001, SQLite 2.0 replaced gdbm with a custom [[B-tree]] [[Implementation|implémentation]], adding [[Database transaction|transaction]] capability. In June 2004, SQLite 3.0 added [[Internationalization and localization|internationalization]], [[manifest typing]], and other major improvements, partially funded by [[America Online]]. In 2011, Hipp announced his plans to add a [[NoSQL]] interface to SQLite, as well as announcing UnQL, a functional superset of [[SQL]] designed for [[document-oriented databases]].<ref name="unql-interview">{{cite web |url=http://www.infoq.com/news/2011/08/UnQL |title=Interview: Richard Hipp on UnQL, a New Query Language for Document Databases |publisher=InfoQ |date=August 4, 2011 |access-date=October 5, 2011}}</ref>
In August 2000, version 1.0 of SQLite was released, with storage based on [[gdbm]] (GNU Database Manager). In September 2001, SQLite 2.0 replaced gdbm with a custom [[B-tree]] implementation, adding [[Database transaction|transaction]] capability. In June 2004, SQLite 3.0 added [[Internationalization and localization|internationalization]], [[manifest typing]], and other major improvements, partially funded by [[America Online]]. In 2011, Hipp announced his plans to add a [[NoSQL]] interface to SQLite, as well as announcing UnQL, a functional superset of [[SQL]] designed for [[document-oriented databases]].<ref name="unql-interview">{{cite web |url=http://www.infoq.com/news/2011/08/UnQL |title=Interview: Richard Hipp on UnQL, a New Query Language for Document Databases |publisher=InfoQ |date=August 4, 2011 |access-date=October 5, 2011 |archive-date=April 8, 2014 |archive-url=https://web.archive.org/web/20140408215240/http://www.infoq.com/news/2011/08/UnQL |url-status=live }}</ref> In 2018, SQLite adopted a Code of Conduct based on the [[Rule of Saint Benedict]] which caused some controversy and was later renamed as a Code of Ethics.<ref>{{Cite web |last=McCarthy |first=Kieren |title=SQLite creator crucified after code of conduct warns devs to love God, and not kill, commit adultery, steal, curse... |url=https://www.theregister.com/2018/10/22/sqlite_code_of_conduct/ |access-date=2022-11-17 |website=www.theregister.com |language=en |archive-date=2022-11-17 |archive-url=https://web.archive.org/web/20221117120853/https://www.theregister.com/2018/10/22/sqlite_code_of_conduct/ |url-status=live }}</ref>


SQLite is one of four formats recommended for long-term storage of [[Data set|datasets]] approved for use by the [[Library of Congress]].<ref>{{Cite web |url=https://www.sqlite.org/locrsf.html |title=LoC Recommended Storage Format |website=www.sqlite.org |access-date=2020-04-09}}</ref><ref>{{Cite web |url=https://www.loc.gov/preservation/digital/formats/fdd/fdd000461.shtml |title=SQLite, Version 3 |date=2017-03-28 |website=www.loc.gov |access-date=2020-04-09}}</ref><ref>{{Cite web |url=https://www.loc.gov/preservation/resources/rfs/data.html |title=Recommended Formats Statement – datasets/databases |publisher=Library of Congress |access-date=2020-04-09}}</ref>
SQLite is one of four formats recommended for long-term storage of [[Data set|datasets]] approved for use by the [[Library of Congress]].<ref>{{Cite web |url=https://www.sqlite.org/locrsf.html |title=LoC Recommended Storage Format |website=www.sqlite.org |access-date=2020-04-09 |archive-date=2020-04-23 |archive-url=https://web.archive.org/web/20200423212849/https://www.sqlite.org/locrsf.html |url-status=live }}</ref><ref>{{Cite web |url=https://www.loc.gov/preservation/digital/formats/fdd/fdd000461.shtml |title=SQLite, Version 3 |date=2017-03-28 |website=www.loc.gov |access-date=2020-04-09 |archive-date=2020-05-11 |archive-url=https://web.archive.org/web/20200511194518/https://www.loc.gov/preservation/digital/formats/fdd/fdd000461.shtml |url-status=live }}</ref><ref>{{Cite web |url=https://www.loc.gov/preservation/resources/rfs/data.html |title=Recommended Formats Statement – datasets/databases |publisher=Library of Congress |access-date=2020-04-09 |archive-date=2018-08-22 |archive-url=https://web.archive.org/web/20180822113435/https://www.loc.gov/preservation/resources/rfs/data.html |url-status=live }}</ref>


==Design==
==Design==
SQLite was designed to allow the program to be operated without installing a database management system or requiring a [[database administrator]]. Unlike [[Client–server model|client–server]] database management systems, the SQLite engine has no standalone [[process (computing)|process]]es with which the application program communicates. Instead, a [[Linker (computing)|linker]] integrates the SQLite library {{emdash}} [[static library|statically]] or [[dynamic linker|dynamically]] {{emdash}} into an application program which uses SQLite's functionality through simple [[subroutine|function calls]], reducing [[latency (engineering)|latency]] in database operations; for simple queries with little concurrency, SQLite [[Computer performance|performance]] profits from avoiding the overhead of [[inter-process communication]].
SQLite was designed to allow the program to be operated without installing a database management system or requiring a [[database administrator]]. Unlike [[Client–server model|client–server]] database management systems, the SQLite engine has no standalone [[process (computing)|process]]es with which the application program communicates. Instead, a [[Linker (computing)|linker]] integrates the SQLite library {{emdash}} [[static library|statically]] or [[dynamic linker|dynamically]] {{emdash}} into an application program which uses SQLite's functionality through simple [[subroutine|function calls]], reducing [[latency (engineering)|latency]] in database operations; for simple queries with little concurrency, SQLite [[Computer performance|performance]] profits from avoiding the overhead of [[inter-process communication]].


Due to the serverless design, SQLite applications require less configuration than client–server databases. SQLite is called ''zero-conf''<ref>{{cite web |title = SQLite Is A Zero-Configuration Database |url = https://sqlite.org/zeroconf.html |access-date = August 3, 2015 |publisher = SQLite.org}}</ref> because it does not require service management (such as startup scripts) or access control based on [[Data control language|GRANT]] and passwords. [[Access-control list|Access control]] is handled by means of [[file-system permissions]] given to the database file itself. Databases in client–server systems use [[File system|file-system]] permissions that give access to the database files only to the [[Daemon (computing)|daemon]] process, which handles its locks internally, allowing [[Concurrency (computer science)|concurrent]] writes from several processes.
Due to the serverless design, SQLite applications require less configuration than client–server databases. SQLite is called ''zero-conf''<ref>{{cite web |title = SQLite Is A Zero-Configuration Database |url = https://sqlite.org/zeroconf.html |access-date = August 3, 2015 |publisher = SQLite.org |archive-date = May 2, 2024 |archive-url = https://web.archive.org/web/20240502210736/https://sqlite.org/zeroconf.html |url-status = live }}</ref> because it does not require service management (such as startup scripts) or access control based on [[Data control language|GRANT]] and passwords. [[Access-control list|Access control]] is handled by means of [[file-system permissions]] given to the database file itself. Databases in client–server systems use [[File system|file-system]] permissions that give access to the database files only to the [[Daemon (computing)|daemon]] process, which handles its locks internally, allowing [[Concurrency (computer science)|concurrent]] writes from several processes.


SQLite stores the whole database (definitions, [[Table (database)|tables]], indices, and the data itself) as a single [[Cross-platform software|cross-platform]] file on a host machine, allowing several processes or [[thread (computer science)|threads]] to access the same database concurrently. It implements this simple design by [[lock (computer science)|locking]] the database file during writing. Write access may fail with an [[error code]], or it can be retried until a configurable timeout expires. SQLite read operations can be [[Computer multitasking|multitasked]], though due to the serverless design, writes can only be performed sequentially. This concurrent access restriction does not apply to temporary tables, and it is relaxed in version 3.7 as [[write-ahead logging]] (WAL) enables concurrent reads and writes.<ref>{{cite web |url = https://sqlite.org/wal.html |title = Write Ahead Logging in SQLite 3.7 |publisher = SQLite.org |access-date = September 3, 2011 |quote = WAL provides more concurrency as readers do not block writers and a writer does not block readers. Reading and writing can proceed concurrently.}}</ref> Since SQLite has to rely on file-system locks, it is not the preferred choice for write-intensive deployments.<ref>{{cite web |title = Appropriate Uses For SQLite |url = https://sqlite.org/whentouse.html |access-date = 2015-09-03 |publisher = SQLite.org}}</ref>
SQLite stores the whole database (definitions, [[Table (database)|tables]], indices, and the data itself) as a single [[Cross-platform software|cross-platform]] file on a host machine, allowing several processes or [[thread (computer science)|threads]] to access the same database concurrently. It implements this simple design by [[lock (computer science)|locking]] the database file during writing. Write access may fail with an [[error code]], or it can be retried until a configurable timeout expires. SQLite read operations can be [[Computer multitasking|multitasked]], though due to the serverless design, writes can only be performed sequentially. This concurrent access restriction does not apply to temporary tables, and it is relaxed in version 3.7 as [[write-ahead logging]] (WAL) enables concurrent reads and writes.<ref>{{cite web |url = https://sqlite.org/wal.html |title = Write Ahead Logging in SQLite 3.7 |publisher = SQLite.org |access-date = September 3, 2011 |quote = WAL provides more concurrency as readers do not block writers and a writer does not block readers. Reading and writing can proceed concurrently. |archive-date = May 2, 2024 |archive-url = https://web.archive.org/web/20240502210711/https://sqlite.org/wal.html |url-status = live }}</ref> Since SQLite has to rely on file-system locks, it is not the preferred choice for write-intensive deployments.<ref>{{cite web |title = Appropriate Uses For SQLite |url = https://sqlite.org/whentouse.html |access-date = 2015-09-03 |publisher = SQLite.org |archive-date = 2024-05-02 |archive-url = https://web.archive.org/web/20240502210713/https://sqlite.org/whentouse.html |url-status = live }}</ref>


SQLite uses [[PostgreSQL]] as a reference platform. "What would PostgreSQL do" is used to make sense of the SQL standard.<ref>{{cite web |url=https://lwn.net/Articles/601144/ |title=PGCon 2014: Clustering and VODKA |website=Lwn.net |access-date=2017-01-06}}</ref><ref>{{cite web |url=https://www.pgcon.org/2014/schedule/events/736.en.html |title=PGCon2014: SQLite: Protégé of PostgreSQL |website=Pgcon.org |date=20 September 2015 |access-date=2017-01-06}}</ref> One major deviation is that, with the exception of [[primary key]]s, SQLite does not enforce [[type checking]]; the type of a value is dynamic and not strictly constrained by the [[database schema|schema]] (although the schema will trigger a conversion when storing, if such a conversion is potentially reversible). SQLite strives to follow [[Robustness principle|Postel's rule]].<ref name=":1" />
SQLite uses [[PostgreSQL]] as a reference platform. "What would PostgreSQL do" is used to make sense of the SQL standard.<ref>{{cite web |url=https://lwn.net/Articles/601144/ |title=PGCon 2014: Clustering and VODKA |website=Lwn.net |access-date=2017-01-06 |archive-date=2015-06-29 |archive-url=https://web.archive.org/web/20150629195442/https://lwn.net/Articles/601144/ |url-status=live }}</ref><ref>{{cite web |url=https://www.pgcon.org/2014/schedule/events/736.en.html |title=PGCon2014: SQLite: Protégé of PostgreSQL |website=Pgcon.org |date=20 September 2015 |access-date=2017-01-06 |archive-date=2014-12-30 |archive-url=https://web.archive.org/web/20141230193958/http://www.pgcon.org/2014/schedule/events/736.en.html |url-status=live }}</ref> One major deviation is that, with the exception of [[primary key]]s, SQLite does not enforce [[type checking]]; the type of a value is dynamic and not strictly constrained by the [[database schema|schema]] (although the schema will trigger a conversion when storing, if such a conversion is potentially reversible). SQLite strives to follow [[Robustness principle|Postel's rule]].<ref name=":1" />


==Features==
==Features==
SQLite implements most of the [[SQL-92]] standard for SQL, but lacks some features. For example, it only partially provides [[database trigger|triggers]] and cannot write to [[view (database)|views]] (however, it provides INSTEAD OF triggers that provide this functionality). Its support of [[Data definition language#ALTER statement|ALTER TABLE]] statements is limited.<ref>{{Cite web|url=https://www.sqlite.org/changes.html|title = Release History of SQLite}}</ref>
SQLite implements most of the [[SQL-92]] standard for SQL, but lacks some features. For example, it only partially provides [[database trigger|triggers]] and cannot write to [[view (database)|views]] (however, it provides INSTEAD OF triggers that provide this functionality). Its support of [[Data definition language#ALTER statement|ALTER TABLE]] statements is limited.<ref>{{Cite web|url=https://www.sqlite.org/changes.html|title=Release History of SQLite|access-date=2021-03-22|archive-date=2021-03-16|archive-url=https://web.archive.org/web/20210316043517/https://www.sqlite.org/changes.html|url-status=live}}</ref>


SQLite uses an unusual [[type system]] for a SQL-compatible DBMS: instead of assigning a [[SQL data types|type]] to a column as in most SQL database systems, types are assigned to individual values; in language terms it is ''dynamically typed''. Moreover, it is ''weakly typed'' in some of the same ways that [[Perl]] is: one can insert a [[string (computer science)|string]] into an [[Integer (computer science)|integer]] column (although SQLite will try to convert the string to an integer first, if the column's preferred type is integer). This adds flexibility to columns, especially when bound to a dynamically typed scripting language. However, the technique is not portable to other SQL products. A common criticism is that SQLite's type system lacks the [[data integrity]] mechanism provided by statically typed columns, although it can be emulated with constraints like <code>CHECK(typeof(x)='integer')</code>.<ref name="Owens06" /> Strict tables were added in version 3.37.1.<ref name=":1">{{cite web |title = SQLite: StrictMode |url = https://sqlite.org/src/wiki?name=StrictMode |website=Sqlite.org |access-date = September 3, 2015}}</ref>
SQLite uses an unusual [[type system]] for an SQL-compatible DBMS: instead of assigning a [[SQL data types|type]] to a column as in most SQL database systems, types are assigned to individual values; in language terms it is ''dynamically typed''. Moreover, it is ''weakly typed'' in some of the same ways that [[Perl]] is: one can insert a [[string (computer science)|string]] into an [[Integer (computer science)|integer]] column (although SQLite will try to convert the string to an integer first, if the column's preferred type is integer). This adds flexibility to columns, especially when bound to a dynamically typed scripting language. However, the technique is not portable to other SQL products. A common criticism is that SQLite's type system lacks the [[data integrity]] mechanism provided by statically typed columns, although it can be emulated with constraints like {{code|2=sql|1=CHECK(typeof(x)='integer')}}.<ref name="Owens06" /> Strict tables were added in version 3.37.1.<ref name=":1">{{cite web |title = SQLite: StrictMode |url = https://sqlite.org/src/wiki?name=StrictMode |website = Sqlite.org |access-date = September 3, 2015 |archive-date = March 4, 2016 |archive-url = https://web.archive.org/web/20160304115940/https://sqlite.org/src/wiki?name=StrictMode |url-status = live }}</ref>


Tables normally include a hidden ''rowid'' index column, which gives faster access.<ref>{{cite web |title=SQL As Understood By SQLite |url=https://www.sqlite.org/lang_createtable.html#rowid |website=SQLite |access-date=21 May 2018 |quote=Searching for a record with a specific rowid, or for all records with rowids within a specified range is around twice as fast as a similar search made by specifying any other PRIMARY KEY or indexed value.}}</ref> If a database includes an Integer Primary Key column, SQLite will typically optimize it by treating it as an alias for ''rowid'', causing the contents to be stored as a [[strictly typed]] 64-bit signed integer and changing its behavior to be somewhat like an auto-incrementing column. Future{{when|date=August 2019}} versions of SQLite may include a command to introspect whether a column has behavior like that of ''rowid'' to differentiate these columns from weakly typed, non-autoincrementing Integer Primary Keys.<ref>{{cite web |url=https://www.sqlite.org/src/info/2494132a2b1221a4 |title=SQLite: Check-in [2494132a] |quote=Add the "PRAGMA table_ipk(TABLE)" command for evaluation purposes. |website=www.sqlite.org |date=2017-11-28}}</ref>{{failed verification|date=August 2019}}
Tables normally include a hidden ''rowid'' index column, which gives faster access.<ref>{{cite web |title=SQL As Understood By SQLite |url=https://www.sqlite.org/lang_createtable.html#rowid |website=SQLite |access-date=21 May 2018 |quote=Searching for a record with a specific rowid, or for all records with rowids within a specified range is around twice as fast as a similar search made by specifying any other PRIMARY KEY or indexed value. |archive-date=21 May 2018 |archive-url=https://web.archive.org/web/20180521104530/https://www.sqlite.org/lang_createtable.html#rowid |url-status=live }}</ref> If a database includes an Integer Primary Key column, SQLite will typically optimize it by treating it as an alias for ''rowid'', causing the contents to be stored as a [[strictly typed]] 64-bit signed integer and changing its behavior to be somewhat like an auto-incrementing column. Future{{when|date=August 2019}} versions of SQLite may include a command to introspect whether a column has behavior like that of ''rowid'' to differentiate these columns from weakly typed, non-autoincrementing Integer Primary Keys.<ref>{{cite web |url=https://www.sqlite.org/src/info/2494132a2b1221a4 |title=SQLite: Check-in [2494132a] |quote=Add the "PRAGMA table_ipk(TABLE)" command for evaluation purposes. |website=www.sqlite.org |date=2017-11-28 |access-date=2018-05-21 |archive-date=2018-05-21 |archive-url=https://web.archive.org/web/20180521104641/https://www.sqlite.org/src/info/2494132a2b1221a4 |url-status=live }}</ref>{{failed verification|date=August 2019}}


Version 3.6.19 released on October 14, 2009 added support for foreign key constraints.<ref>{{cite book |last=Karwin |first=Bill |editor-last=Carter |editor-first=Jacquelyn |date=May 2010 |title=SQL Antipatterns: Avoiding the Pitfalls of Database Programming |publisher=The Pragmatic Bookshelf |isbn=978-1-934356-55-5 |page=70 |quote=Sometimes you're forced to use a database brand that doesn't support foreign key constraints (for example MySQL's MyISAM storage engine or SQLite prior to version 3.6.19).}}</ref><ref>{{Cite web|url=https://sqlite.org/releaselog/3_6_19.html|title=SQLite Release 3.6.19 On 2009-10-14|website=sqlite.org}}</ref>
Version 3.6.19 released on October 14, 2009 added support for foreign key constraints.<ref>{{cite book |last=Karwin |first=Bill |editor-last=Carter |editor-first=Jacquelyn |date=May 2010 |title=SQL Antipatterns: Avoiding the Pitfalls of Database Programming |publisher=The Pragmatic Bookshelf |isbn=978-1-934356-55-5 |page=70 |quote=Sometimes you're forced to use a database brand that doesn't support foreign key constraints (for example MySQL's MyISAM storage engine or SQLite prior to version 3.6.19).}}</ref><ref>{{Cite web|url=https://sqlite.org/releaselog/3_6_19.html|title=SQLite Release 3.6.19 On 2009-10-14|website=sqlite.org|access-date=2020-10-15|archive-date=2020-10-29|archive-url=https://web.archive.org/web/20201029060401/http://sqlite.org/releaselog/3_6_19.html|url-status=live}}</ref>


[[Stored procedure]]s are not supported; this is an explicit choice by the developers to favor simplicity, as the typical use case of SQLite is to be embedded inside a host application that can define its own procedures around the database.<ref>Source: developers' comments on [https://sqlite.org/forum/info/78a60bdeec7c1ee9 SQLite forum] {{Webarchive|url=https://web.archive.org/web/20230401220416/https://sqlite.org/forum/info/78a60bdeec7c1ee9 |date=2023-04-01 }}</ref>
Full support for [[Unicode]] case-conversions can be enabled through an optional extension.<ref>{{cite web |title = Case-insensitive matching of Unicode characters does not work |url = https://sqlite.org/faq.html#q18 |website = SQLite Frequently Asked Questions |access-date = 2015-09-03}}</ref>


Full support for [[Unicode]] case-conversions can be enabled through an optional extension.<ref>{{cite web |title = Case-insensitive matching of Unicode characters does not work |url = https://sqlite.org/faq.html#q18 |website = SQLite Frequently Asked Questions |access-date = 2015-09-03 |archive-date = 2015-09-05 |archive-url = https://web.archive.org/web/20150905054749/http://www.sqlite.org/faq.html#q18 |url-status = live }}</ref>
SQLite version 3.7.4 first saw the addition of the FTS4 ([[full-text search]]) module, which features enhancements over the older FTS3 module.<ref>{{cite web |title = SQLite Release 3.7.4 On 2010-12-08 |url = https://sqlite.org/releaselog/3_7_4.html |access-date = September 3, 2015 |date = December 8, 2010 |publisher = SQLite.org}}</ref> FTS4 allows users to perform full-text searches on documents similar to how [[Search engine|search engines]] search webpages.<ref>{{cite web |title = SQLite FTS3 and FTS4 Extensions |url = https://sqlite.org/fts3.html |access-date = September 3, 2015 |publisher = SQLite.org}}</ref> Version 3.8.2 added support for creating tables without [[Pseudocolumn|rowid]],<ref>{{cite web |title = SQLite Release 3.8.2 On 2013-12-06 |url = https://sqlite.org/releaselog/3_8_2.html |access-date = September 3, 2015 |date = December 6, 2013 |publisher = SQLite.org}}</ref> which may provide space and performance improvements.<ref>{{cite web |title = The WITHOUT ROWID Optimization |url = https://sqlite.org/withoutrowid.html |access-date = September 3, 2015 |publisher = SQLite.org}}</ref> [[Common table expressions]] support was added to SQLite in version 3.8.3.<ref>{{cite web |title = SQLite Release 3.8.3 On 2014-02-03 |url = https://sqlite.org/releaselog/3_8_3.html |access-date = September 3, 2015 |date = February 3, 2014 |publisher = SQLite.org}}</ref> 3.8.11 added a newer search module called FTS5, the more radical (compared to FTS4) changes requiring a bump in version.


SQLite version 3.7.4 first saw the addition of the FTS4 ([[full-text search]]) module, which features enhancements over the older FTS3 module.<ref>{{cite web |title = SQLite Release 3.7.4 On 2010-12-08 |url = https://sqlite.org/releaselog/3_7_4.html |access-date = September 3, 2015 |date = December 8, 2010 |publisher = SQLite.org |archive-date = September 16, 2015 |archive-url = https://web.archive.org/web/20150916212345/http://www.sqlite.org/releaselog/3_7_4.html |url-status = live }}</ref> FTS4 allows users to perform full-text searches on documents similar to how [[Search engine|search engines]] search webpages.<ref>{{cite web |title = SQLite FTS3 and FTS4 Extensions |url = https://sqlite.org/fts3.html |access-date = September 3, 2015 |publisher = SQLite.org |archive-date = September 5, 2015 |archive-url = https://web.archive.org/web/20150905095801/http://www.sqlite.org/fts3.html |url-status = live }}</ref> Version 3.8.2 added support for creating tables without [[Pseudocolumn|rowid]],<ref>{{cite web |title = SQLite Release 3.8.2 On 2013-12-06 |url = https://sqlite.org/releaselog/3_8_2.html |access-date = September 3, 2015 |date = December 6, 2013 |publisher = SQLite.org |archive-date = September 24, 2015 |archive-url = https://web.archive.org/web/20150924105132/http://www.sqlite.org/releaselog/3_8_2.html |url-status = live }}</ref> which may provide space and performance improvements.<ref>{{cite web |title = The WITHOUT ROWID Optimization |url = https://sqlite.org/withoutrowid.html |access-date = September 3, 2015 |publisher = SQLite.org |archive-date = September 5, 2015 |archive-url = https://web.archive.org/web/20150905093326/http://www.sqlite.org/withoutrowid.html |url-status = live }}</ref> [[Common table expressions]] support was added to SQLite in version 3.8.3.<ref>{{cite web |title = SQLite Release 3.8.3 On 2014-02-03 |url = https://sqlite.org/releaselog/3_8_3.html |access-date = September 3, 2015 |date = February 3, 2014 |publisher = SQLite.org |archive-date = September 5, 2015 |archive-url = https://web.archive.org/web/20150905093435/http://www.sqlite.org/releaselog/3_8_3.html |url-status = live }}</ref> 3.8.11 added a newer search module called FTS5, the more radical (compared to FTS4) changes requiring a bump in version.
In 2015, with the ''json1 extension''<ref>{{cite web |url=https://sqlite.org/json1.html |title=The JSON1 Extension |website=SQLite.org}}</ref> and new subtype interfaces, SQLite version 3.9 introduced [[JSON]] content managing.


In 2015, with the ''json1 extension''<ref>{{cite web |url=https://sqlite.org/json1.html |title=The JSON1 Extension |website=SQLite.org |access-date=2017-09-14 |archive-date=2017-09-14 |archive-url=https://web.archive.org/web/20170914125149/https://sqlite.org/json1.html |url-status=live }}</ref> and new subtype interfaces, SQLite version 3.9 introduced [[JSON]] content managing.
As of version 3.33.0, the maximum supported database size is 281 [[Units of information|TB]].<ref>{{cite web|url=https://www.sqlite.org/limits.html |title=Limits In SQLite|website=SQLite.org}}</ref>

As of version 3.33.0, the maximum supported database size is 281 [[Units of information|TB]].<ref>{{cite web|url=https://www.sqlite.org/limits.html|title=Limits In SQLite|website=SQLite.org|access-date=2022-09-19|archive-date=2021-11-07|archive-url=https://web.archive.org/web/20211107064937/https://sqlite.org/limits.html|url-status=live}}</ref>


==Development and distribution==
==Development and distribution==
SQLite's code is hosted with [[Fossil (software)|Fossil]], a [[distributed version control system]] that uses SQLite as a local cache for its non-relational database format, and SQLite's SQL as an implementation language.<ref>{{cite web|url = https://www.fossil-scm.org/home/doc/trunk/www/theory1.wiki|title = Thoughts On The Design Of The Fossil DVCS|publisher = Fossil-scm.org|date = July 12, 2017|access-date = October 14, 2022}}</ref><ref>{{cite web|url = https://www.fossil-scm.org/index.html/doc/tip/www/stats.wiki|title = Fossil: Fossil Performance|publisher = Fossil-scm.org|date = August 23, 2009|access-date = September 12, 2009}}</ref>
SQLite's code is hosted with [[Fossil (software)|Fossil]], a [[distributed version control system]] that uses SQLite as a local cache for its non-relational database format, and SQLite's SQL as an implementation language.<ref>{{cite web|url = https://www.fossil-scm.org/home/doc/trunk/www/theory1.wiki|title = Thoughts On The Design Of The Fossil DVCS|publisher = Fossil-scm.org|date = July 12, 2017|access-date = October 14, 2022|archive-date = October 13, 2022|archive-url = https://web.archive.org/web/20221013234319/https://www.fossil-scm.org/home/doc/trunk/www/theory1.wiki|url-status = live}}</ref><ref>{{cite web|url = https://www.fossil-scm.org/index.html/doc/tip/www/stats.wiki|title = Fossil: Fossil Performance|publisher = Fossil-scm.org|date = August 23, 2009|access-date = September 12, 2009|archive-date = October 9, 2009|archive-url = https://web.archive.org/web/20091009054952/http://www.fossil-scm.org/index.html/doc/tip/www/stats.wiki|url-status = live}}</ref>

SQLite is [[Public-domain software|public domain]], but not "open-contribution", with the website stating "the project does not accept patches from people who have not submitted an [[affidavit]] dedicating their contribution into the public domain."<ref>{{Cite web |title=SQLite Copyright |url=https://sqlite.org/copyright.html |access-date=2024-03-06 |website=sqlite.org |archive-date=2024-03-15 |archive-url=https://web.archive.org/web/20240315172355/https://www.sqlite.org/copyright.html |url-status=live }}</ref> Instead of a [[code of conduct]], the founders have adopted a [[ethical code|code of ethics]] based on the [[Rule of Saint Benedict|Rule of St. Benedict]].<ref>{{Cite web |title=Code Of Ethics |url=https://sqlite.org/codeofethics.html |access-date=2024-03-06 |website=sqlite.org |archive-date=2024-02-19 |archive-url=https://web.archive.org/web/20240219225117/https://sqlite.org/codeofethics.html |url-status=live }}</ref>


A standalone [[Console application|command-line]] [[Shell (computing)|shell]] program called ''sqlite3''<ref>{{cite web|url = https://www.sqlite.org/cli.html|title = Command Line Shell For SQLite |publisher = Sqlite.org|access-date = October 14, 2022}}</ref> is provided in SQLite's distribution. It can be used to create a database, define tables, insert and change rows, run queries and manage an SQLite database file. It also serves as an example for writing applications that use the SQLite library.
A standalone [[Console application|command-line]] [[Shell (computing)|shell]] program called ''sqlite3''<ref>{{cite web|url = https://www.sqlite.org/cli.html|title = Command Line Shell For SQLite|publisher = Sqlite.org|access-date = October 14, 2022|archive-date = October 6, 2022|archive-url = https://web.archive.org/web/20221006104551/https://www.sqlite.org/cli.html|url-status = live}}</ref> is provided in SQLite's distribution. It can be used to create a database, define tables, insert and change rows, run queries and manage an SQLite database file. It also serves as an example for writing applications that use the SQLite library.


SQLite uses automated [[regression testing]] prior to each release. Over 2 million tests<ref name=tests>{{cite web |url = https://sqlite.org/testing.html |title = How SQLite Is Tested |publisher = SQLite.org |access-date = September 12, 2009}}</ref> are run as part of a release's verification. Starting with the August 10, 2009 release of SQLite 3.6.17, SQLite releases have 100% branch test coverage, one of the components of [[code coverage]]. The tests and [[test harness]]es are partially public-domain and partially [[proprietary software|proprietary]].<ref name=tests />
SQLite uses automated [[regression testing]] prior to each release. Over 2 million tests<ref name=tests>{{cite web |url = https://sqlite.org/testing.html |title = How SQLite Is Tested |publisher = SQLite.org |access-date = September 12, 2009 |archive-date = October 6, 2009 |archive-url = https://web.archive.org/web/20091006224147/http://www.sqlite.org/testing.html |url-status = live }}</ref> are run as part of a release's verification. Starting with the August 10, 2009 release of SQLite 3.6.17, SQLite releases have 100% branch test coverage, one of the components of [[code coverage]]. The tests and [[test harness]]es are partially public-domain and partially [[proprietary software|proprietary]].<ref name=tests />


=={{anchor|Adoption}}Notable uses==
=={{anchor|Adoption}}Notable uses==
Line 101: Line 113:
* [[illumos]]
* [[illumos]]
* [[iOS]]
* [[iOS]]
* [[Mac OS X 10.4]] onwards (Apple adopted it as an option in [[macOS]]'s [[Core Data]] API from the original implementation)
* [[Mac OS X 10.4]] onwards (Apple adopted it as an option in [[macOS]]'s [[Core Data]] API from the original implementation)
* [[Maemo]]
* [[Maemo]]
* [[MeeGo]]
* [[MeeGo]]
* [[MorphOS]] since version 3.10
* [[MorphOS]] 3.10 onwards
* [[NetBSD]]
* [[NetBSD]]
* [[NixOS]] where it is used by the [[Nix (package manager)|Nix]] core package management system
* [[NixOS]] where it is used by the [[Nix (package manager)|Nix]] core package management system
Line 112: Line 124:
* [[Tizen]]
* [[Tizen]]
* [[webOS]]
* [[webOS]]
* [[Windows 10]] onwards <ref>{{cite web |url=https://docs.microsoft.com/en-us/windows/uwp/data-access/sqlite-databases#to-use-the-version-of-sqlite-that-is-installed-with-windows | title=To use the version of SQLite that is installed with Windows}}</ref>
* [[Windows 10]] onwards<ref>{{cite web| url=https://docs.microsoft.com/en-us/windows/uwp/data-access/sqlite-databases#to-use-the-version-of-sqlite-that-is-installed-with-windows| title=To use the version of SQLite that is installed with Windows| date=20 October 2022| access-date=31 March 2022| archive-date=31 March 2022| archive-url=https://web.archive.org/web/20220331170828/https://docs.microsoft.com/en-us/windows/uwp/data-access/sqlite-databases#to-use-the-version-of-sqlite-that-is-installed-with-windows| url-status=live}}</ref>


===Middleware===
===Middleware===
* [[ADO.NET]] adapter, initially developed by Robert Simpson, is maintained jointly with the SQLite developers since April 2010.<ref>{{cite web|url=http://system.data.sqlite.org/index.html/doc/trunk/www/index.wiki |title=Home |website=System.Data.SQLite |date=2016-12-30 |access-date=2017-01-06}}</ref>
* [[ADO.NET]] adapter, initially developed by Robert Simpson, is maintained jointly with the SQLite developers since April 2010.<ref>{{cite web |url=http://system.data.sqlite.org/index.html/doc/trunk/www/index.wiki |title=Home |website=System.Data.SQLite |date=2016-12-30 |access-date=2017-01-06 |archive-date=2014-07-13 |archive-url=https://web.archive.org/web/20140713080835/http://system.data.sqlite.org/index.html/doc/trunk/www/index.wiki |url-status=live }}</ref>
* [[ODBC]] driver has been developed and is maintained separately by Christian Werner.<ref>{{cite web|url=http://www.ch-werner.de/sqliteodbc/ |title=SQLite ODBC Driver |website=Ch-werner.de |date=2016-12-01 |access-date=2017-01-06}}</ref> Werner's ODBC driver is the recommended connection method for accessing SQLite from [[OpenOffice.org]].<ref>{{cite web|url=http://documentation.openoffice.org/HOW_TO/data_source/SQLite.pdf |title=Using SQLite Database with OpenOffice.org : Version 2.0 |website=Documentation.openoffice.org |access-date=2017-01-06}}</ref>
* [[ODBC]] driver has been developed and is maintained separately by Christian Werner.<ref>{{cite web |url=http://www.ch-werner.de/sqliteodbc/ |title=SQLite ODBC Driver |website=Ch-werner.de |date=2016-12-01 |access-date=2017-01-06 |archive-date=2014-06-26 |archive-url=https://web.archive.org/web/20140626165719/http://www.ch-werner.de/sqliteodbc/ |url-status=live }}</ref> Werner's ODBC driver is the recommended connection method for accessing SQLite from [[OpenOffice.org]].<ref>{{cite web |url=http://documentation.openoffice.org/HOW_TO/data_source/SQLite.pdf |title=Using SQLite Database with OpenOffice.org : Version 2.0 |website=Documentation.openoffice.org |access-date=2017-01-06 |archive-date=2011-09-28 |archive-url=https://web.archive.org/web/20110928073029/http://documentation.openoffice.org/HOW_TO/data_source/SQLite.pdf |url-status=live }}</ref>
* [[Component Object Model|COM]] ([[ActiveX]]) wrapper making SQLite accessible on Windows to scripted languages such as [[JScript]] and [[VBScript]]. This adds SQLite database capabilities to [[HTML Application]]s (HTA).<ref>{{cite web |url = https://sqlite.org/cvstrac/wiki?p=SqliteWrappers|title = sqlite&nbsp;— Sqlite Wrappers|date = February 7, 2009|publisher = SQLite.org|access-date = February 7, 2009}}</ref>
* [[Component Object Model|COM]] ([[ActiveX]]) wrapper making SQLite accessible on Windows to scripted languages such as [[JScript]] and [[VBScript]]. This adds SQLite database capabilities to [[HTML Application]]s (HTA).<ref>{{cite web|url = https://sqlite.org/cvstrac/wiki?p=SqliteWrappers|title = sqlite&nbsp;— Sqlite Wrappers|date = February 7, 2009|publisher = SQLite.org|access-date = February 7, 2009|archive-date = February 5, 2009|archive-url = https://web.archive.org/web/20090205225756/http://sqlite.org/cvstrac/wiki?p=SqliteWrappers|url-status = live}}</ref>


===Web browsers===
===Web browsers===
* The browsers [[Google Chrome]], [[Opera (web browser)|Opera]], [[Safari (web browser)|Safari]] and the [[Android Browser]] all allow for storing information in, and retrieving it from, a SQLite database within the browser, using the [[Web SQL Database]] technology, although this is rapidly becoming deprecated (namely superseded by [[IndexedDB]]). Internally, these [[Chromium (web browser)|Chromium]] based browsers use SQLite databases for storing configuration data like site visit history, cookies, download history etc.<ref>{{cite web|url=https://www.foxtonforensics.com/browser-history-examiner/chrome-history-location |title=Location of Google Chrome history |website=www.foxtonforensics.com |date=2020-10-06 |access-date=2020-10-06}}</ref>
* The browsers [[Google Chrome]], [[Opera (web browser)|Opera]], [[Safari (web browser)|Safari]] and the [[Android Browser]] all allow for storing information in, and retrieving it from, an SQLite database within the browser, using the official SQLite Wasm ([[WebAssembly]]) build,<ref>{{Cite web
| url = https://sqlite.org/wasm
| title = sqlite3 WebAssembly & JavaScript Documentation Index
| website = SQLite
| access-date = 2023-05-08
| archive-date = 2024-05-02
| archive-url = https://web.archive.org/web/20240502210710/https://sqlite.org/wasm/doc/trunk/index.md
| url-status = live
}}</ref> or using the [[Web SQL Database]] technology, although the latter is becoming deprecated (namely superseded by SQLite Wasm or by [[IndexedDB]]). Internally, these [[Chromium (web browser)|Chromium]] based browsers use SQLite databases for storing configuration data like site visit history, cookies, download history etc.<ref>{{cite web |url=https://www.foxtonforensics.com/browser-history-examiner/chrome-history-location |title=Location of Google Chrome history |website=www.foxtonforensics.com |date=2020-10-06 |access-date=2020-10-06 |archive-date=2023-02-28 |archive-url=https://web.archive.org/web/20230228184524/https://www.foxtonforensics.com/browser-history-examiner/chrome-history-location |url-status=live }}</ref>
* [[Mozilla Firefox]] and [[Mozilla Thunderbird]] store a variety of configuration data (bookmarks, cookies, contacts etc.) in internally managed SQLite databases. Until Firefox version 57 ([[History of Firefox#Firefox 57|"Firefox Quantum"]]), there was a third-party add-on that used the API supporting this functionality to provide a user interface for managing arbitrary SQLite databases.<ref>{{cite web|url=https://addons.mozilla.org/en-US/firefox/addon/sqlite-manager/ |title=SQLite Manager :: Add-ons for Firefox |website=Addons.mozilla.org |date=2015-02-28 |access-date=2017-01-06 |url-status=dead |archive-url=https://web.archive.org/web/20170102010658/https://addons.mozilla.org/en-US/firefox/addon/sqlite-manager/ |archive-date=2017-01-02}}</ref>
* [[Mozilla Firefox]] and [[Mozilla Thunderbird]] store a variety of configuration data (bookmarks, cookies, contacts etc.) in internally managed SQLite databases. Until Firefox version 57 ([[History of Firefox#Firefox 57|"Firefox Quantum"]]), there was a third-party add-on that used the API supporting this functionality to provide a user interface for managing arbitrary SQLite databases.<ref>{{cite web|url=https://addons.mozilla.org/en-US/firefox/addon/sqlite-manager/ |title=SQLite Manager :: Add-ons for Firefox |website=Addons.mozilla.org |date=2015-02-28 |access-date=2017-01-06 |url-status=dead |archive-url=https://web.archive.org/web/20170102010658/https://addons.mozilla.org/en-US/firefox/addon/sqlite-manager/ |archive-date=2017-01-02}}</ref>
* Several third-party add-ons can make use of JavaScript APIs to manage SQLite databases.<ref>{{cite web|url=https://addons.mozilla.org/en-US/firefox/addon/sqlite-manager-webext/ |title=SQLite Manager – Get this Extension for 🦊 Firefox (en-US) |website=Addons.mozilla.org |date=2018-07-24 |access-date=2018-10-05}}</ref><ref>{{cite web|url=https://addons.mozilla.org/en-US/firefox/addon/sql-reader/ |title=SQLite Reader – Get this Extension for 🦊 Firefox (en-US) |website=Addons.mozilla.org |date=2018-09-01 |access-date=2018-10-05}}</ref>
* Several third-party add-ons can make use of [[JavaScript]] APIs to manage SQLite databases.<ref>{{cite web |url=https://addons.mozilla.org/en-US/firefox/addon/sqlite-manager-webext/ |title=SQLite Manager – Get this Extension for 🦊 Firefox (en-US) |website=Addons.mozilla.org |date=2018-07-24 |access-date=2018-10-05 |archive-date=2018-10-05 |archive-url=https://web.archive.org/web/20181005112443/https://addons.mozilla.org/en-US/firefox/addon/sqlite-manager-webext/ |url-status=live }}</ref><ref>{{cite web |url=https://addons.mozilla.org/en-US/firefox/addon/sql-reader/ |title=SQLite Reader – Get this Extension for 🦊 Firefox (en-US) |website=Addons.mozilla.org |date=2018-09-01 |access-date=2018-10-05 |archive-date=2018-10-05 |archive-url=https://web.archive.org/web/20181005112536/https://addons.mozilla.org/en-US/firefox/addon/sql-reader/ |url-status=live }}</ref>


===Web application frameworks===
===Web application frameworks===
* [[Symfony]]
* [[Laravel]]
* [[Laravel]]
* [[Bugzilla]]
* [[Bugzilla]]
Line 132: Line 153:
* [[Ruby on Rails]]'s default database management system
* [[Ruby on Rails]]'s default database management system
* [[web2py]]
* [[web2py]]
* [[Jam.py (web framework)|Jam.py]]


===Others===
===Others===
* [[Adobe Systems]] uses SQLite as its file format in [[Adobe Photoshop Lightroom]], a standard database in [[Adobe AIR]], and internally within [[Adobe Reader]].<ref name=":0">{{cite web|title = Well-Known Users Of SQLite|url = https://sqlite.org/famous.html|access-date = August 5, 2015|publisher = SQLite}}</ref>
* [[Adobe Systems]] uses SQLite as its file format in [[Adobe Photoshop Lightroom]], a standard database in [[Adobe AIR]], and internally within [[Adobe Reader]].<ref name=":0">{{cite web|title = Well-Known Users Of SQLite|url = https://sqlite.org/famous.html|access-date = August 5, 2015|publisher = SQLite|archive-date = July 11, 2015|archive-url = https://web.archive.org/web/20150711135311/http://sqlite.org/famous.html|url-status = live}}</ref>
* As with most Apple software, [[Apple Photos]] uses SQLite internally.<ref name="apple-photos">{{cite web|url = https://simonwillison.net/2020/May/21/dogsheep-photos/|access-date = May 23, 2020|title = Using SQL to find my best photo of a pelican according to Apple Photo|work = Simon Willison’s Weblog}}</ref>
* As with much Apple software, [[Photos (Apple)|Photos]] uses SQLite internally.<ref name="apple-photos">{{cite web|url = https://simonwillison.net/2020/May/21/dogsheep-photos/|access-date = May 23, 2020|title = Using SQL to find my best photo of a pelican according to Apple Photo|work = Simon Willison’s Weblog|archive-date = May 22, 2020|archive-url = https://web.archive.org/web/20200522181550/https://simonwillison.net/2020/May/21/dogsheep-photos/|url-status = live}}</ref>
* [[Audacity (audio editor)|Audacity]] uses SQLite as its file format, as of version 3.0.0.<ref name="audacity">{{cite web|url = https://www.audacityteam.org/audacity-3-0-0-released/|access-date = March 17, 2021|title = Audacity 3.0.0 Released|date = 17 March 2021}}</ref>
* [[Audacity (audio editor)|Audacity]] uses SQLite as its file format, as of version 3.0.0.<ref name="audacity">{{cite web|url = https://www.audacityteam.org/audacity-3-0-0-released/|access-date = March 17, 2021|title = Audacity 3.0.0 Released|date = 17 March 2021|archive-date = 14 August 2023|archive-url = https://web.archive.org/web/20230814021313/https://www.audacityteam.org/audacity-3-0-0-released/|url-status = dead}}</ref>
* [[Evernote]] uses SQLite to store its local database repository in Windows.
* [[Evernote]] uses SQLite to store its local database repository in Windows.
* [[Skype]]<ref name="skype">{{cite mailing list|url = https://www.mail-archive.com/sqlite-users%40sqlite.org/msg27326.html|archive-url=https://web.archive.org/web/20071117061133/https://www.mail-archive.com/sqlite-users%40sqlite.org/msg27326.html|archive-date=2007-11-17|first=Jeremy|last=Hinegardner|title = Skype client using SQLite?|mailing-list=sqlite-users|date = August 28, 2007|access-date = June 14, 2010}}</ref>
* [[Skype]]<ref name="skype">{{cite mailing list|url = https://www.mail-archive.com/sqlite-users%40sqlite.org/msg27326.html|archive-url=https://web.archive.org/web/20071117061133/https://www.mail-archive.com/sqlite-users%40sqlite.org/msg27326.html|archive-date=2007-11-17|first=Jeremy|last=Hinegardner|title = Skype client using SQLite?|mailing-list=sqlite-users|date = August 28, 2007|access-date = June 14, 2010}}</ref>
Line 143: Line 165:
* [[BMW]] [[IDrive]] Sat Nav system
* [[BMW]] [[IDrive]] Sat Nav system
* [[TomTom]] GPS systems, for the [[Navigation Data Standard|NDS]] map data
* [[TomTom]] GPS systems, for the [[Navigation Data Standard|NDS]] map data
* [[Proxmox Virtual Environment|Proxmox VE]] - ''Proxmox Cluster File System'' ([https://pve.proxmox.com/wiki/Proxmox_Cluster_File_System_(pmxcfs) pmxcfs])


==See also==
==See also==
Line 148: Line 171:
* [[Comparison of relational database management systems]]
* [[Comparison of relational database management systems]]
* [[List of relational database management systems]]
* [[List of relational database management systems]]
* [[MySQL]]
* [[SpatiaLite]]
* [[SpatiaLite]]
* [[SQL compliance]]


==References==
==References==
Line 159: Line 182:
{{Refbegin}}
{{Refbegin}}
* {{cite book
* {{cite book
| first1 = Grant
|first1 = Grant
| last1 = Allen
|last1 = Allen
| first2 = Mike
|first2 = Mike
| last2 = Owens
|last2 = Owens
| date = November 5, 2010
|date = November 5, 2010
| title = The Definitive Guide to SQLite
|title = The Definitive Guide to SQLite
| edition = 2nd
|edition = 2nd
| publisher = [[Apress]]
|publisher = [[Apress]]
| page = 368
|page = 368
| isbn = 978-1-4302-3225-4
|isbn = 978-1-4302-3225-4
| url = http://apress.com/book/view/1430232250}}
|url = http://apress.com/book/view/1430232250
|access-date = December 23, 2010
|archive-date = December 30, 2010
|archive-url = https://web.archive.org/web/20101230035043/http://apress.com/book/view/1430232250
|url-status = dead
}}
* {{cite book
* {{cite book
| first1 = Jay A.
|first1 = Jay A.
| last1 = Kreibich
|last1 = Kreibich
| date = August 17, 2010
|date = August 17, 2010
| title = Using SQLite
|title = Using SQLite
| edition = 1st
|edition = 1st
| publisher = [[O'Reilly Media]]
|publisher = [[O'Reilly Media]]
| page = 528
|page = 528
| isbn = 978-0-596-52118-9
|isbn = 978-0-596-52118-9
| url = http://oreilly.com/catalog/9780596521196}}
|url = http://oreilly.com/catalog/9780596521196
|access-date = December 23, 2010
|archive-date = December 25, 2010
|archive-url = https://web.archive.org/web/20101225102001/http://oreilly.com/catalog/9780596521196
|url-status = live
}}
* {{cite book
* {{cite book
| first1 = Chris
|first1 = Chris
| last1 = Newman
|last1 = Newman
| date = November 9, 2004
|date = November 9, 2004
| title = SQLite (Developer's Library)
|title = SQLite (Developer's Library)
| edition = 1st
|edition = 1st
| publisher = [[Sams]]
|publisher = [[Sams]]
| page = 336
|page = 336
| isbn = 0-672-32685-X
|isbn = 0-672-32685-X
| url = http://www.informit.com/store/product.aspx?isbn=067232685X}}
|url = http://www.informit.com/store/product.aspx?isbn=067232685X
|access-date = May 12, 2010
|archive-date = January 14, 2012
|archive-url = https://web.archive.org/web/20120114075902/http://www.informit.com/store/product.aspx?isbn=067232685X
|url-status = live
}}
{{Refend}}
{{Refend}}


Line 195: Line 233:
{{Commons category|}}
{{Commons category|}}
* {{Official website}}
* {{Official website}}
* {{cite web |url=https://corecursive.com/066-sqlite-with-richard-hipp/|title=The Untold Story of SQLite |publisher=CoRecursive}}
* {{curlie|Computers/Software/Databases/SQLite}}


{{Authority control}}
{{Authority control}}
Line 203: Line 241:
[[Category:C (programming language) libraries]]
[[Category:C (programming language) libraries]]
[[Category:Cross-platform free software]]
[[Category:Cross-platform free software]]
[[Category:Database engines]]
[[Category:Embedded databases]]
[[Category:Embedded databases]]
[[Category:Free computer libraries]]
[[Category:Free computer libraries]]

Latest revision as of 17:58, 20 November 2024

SQLite
Developer(s)D. Richard Hipp
Initial release17 August 2000;
24 years ago
 (2000-08-17)
Stable release3.47.2[1] Edit this on Wikidata (7 December 2024; 1 day ago (7 December 2024)) [±]
Repository
Written inC
Operating systemCross-platform
Size699 KiB
TypeRDBMS (embedded)
LicensePublic domain[2]
Websitesqlite.org Edit this at Wikidata
SQLite Database File Format
Filename extension
.sqlite, .sqlite3, .db, .db3, .s3db, .sl3
Internet media typeapplication/vnd.sqlite3[3]
Magic number53 51 4c 69 74 65 20 66 6f 72 6d 61 74 20 33 00 (zero-terminated ASCII "SQLite format 3")
Initial release2004-06-18
Open format?yes (Public Domain)
Websitewww.sqlite.org/fileformat2.html

SQLite (/ˌɛsˌkjuːˌɛlˈt/,[4][5] /ˈskwəˌlt/[6]) is a database engine written in the C programming language. It is not a standalone app; rather, it is a library that software developers embed in their apps. As such, it belongs to the family of embedded databases. It is the most widely deployed database engine, as it is used by several of the top web browsers, operating systems, mobile phones, and other embedded systems.[7]

Many programming languages have bindings to the SQLite library. It generally follows PostgreSQL syntax, but does not enforce type checking by default.[8][9] This means that one can, for example, insert a string into a column defined as an integer.

History

[edit]

D. Richard Hipp designed SQLite in the spring of 2000 while working for General Dynamics on contract with the United States Navy.[10] Hipp was designing software used for a damage-control system aboard guided-missile destroyers; the damage-control system originally used HP-UX with an IBM Informix database back-end. SQLite began as a Tcl extension.[11]

In August 2000, version 1.0 of SQLite was released, with storage based on gdbm (GNU Database Manager). In September 2001, SQLite 2.0 replaced gdbm with a custom B-tree implementation, adding transaction capability. In June 2004, SQLite 3.0 added internationalization, manifest typing, and other major improvements, partially funded by America Online. In 2011, Hipp announced his plans to add a NoSQL interface to SQLite, as well as announcing UnQL, a functional superset of SQL designed for document-oriented databases.[12] In 2018, SQLite adopted a Code of Conduct based on the Rule of Saint Benedict which caused some controversy and was later renamed as a Code of Ethics.[13]

SQLite is one of four formats recommended for long-term storage of datasets approved for use by the Library of Congress.[14][15][16]

Design

[edit]

SQLite was designed to allow the program to be operated without installing a database management system or requiring a database administrator. Unlike client–server database management systems, the SQLite engine has no standalone processes with which the application program communicates. Instead, a linker integrates the SQLite library — statically or dynamically — into an application program which uses SQLite's functionality through simple function calls, reducing latency in database operations; for simple queries with little concurrency, SQLite performance profits from avoiding the overhead of inter-process communication.

Due to the serverless design, SQLite applications require less configuration than client–server databases. SQLite is called zero-conf[17] because it does not require service management (such as startup scripts) or access control based on GRANT and passwords. Access control is handled by means of file-system permissions given to the database file itself. Databases in client–server systems use file-system permissions that give access to the database files only to the daemon process, which handles its locks internally, allowing concurrent writes from several processes.

SQLite stores the whole database (definitions, tables, indices, and the data itself) as a single cross-platform file on a host machine, allowing several processes or threads to access the same database concurrently. It implements this simple design by locking the database file during writing. Write access may fail with an error code, or it can be retried until a configurable timeout expires. SQLite read operations can be multitasked, though due to the serverless design, writes can only be performed sequentially. This concurrent access restriction does not apply to temporary tables, and it is relaxed in version 3.7 as write-ahead logging (WAL) enables concurrent reads and writes.[18] Since SQLite has to rely on file-system locks, it is not the preferred choice for write-intensive deployments.[19]

SQLite uses PostgreSQL as a reference platform. "What would PostgreSQL do" is used to make sense of the SQL standard.[20][21] One major deviation is that, with the exception of primary keys, SQLite does not enforce type checking; the type of a value is dynamic and not strictly constrained by the schema (although the schema will trigger a conversion when storing, if such a conversion is potentially reversible). SQLite strives to follow Postel's rule.[22]

Features

[edit]

SQLite implements most of the SQL-92 standard for SQL, but lacks some features. For example, it only partially provides triggers and cannot write to views (however, it provides INSTEAD OF triggers that provide this functionality). Its support of ALTER TABLE statements is limited.[23]

SQLite uses an unusual type system for an SQL-compatible DBMS: instead of assigning a type to a column as in most SQL database systems, types are assigned to individual values; in language terms it is dynamically typed. Moreover, it is weakly typed in some of the same ways that Perl is: one can insert a string into an integer column (although SQLite will try to convert the string to an integer first, if the column's preferred type is integer). This adds flexibility to columns, especially when bound to a dynamically typed scripting language. However, the technique is not portable to other SQL products. A common criticism is that SQLite's type system lacks the data integrity mechanism provided by statically typed columns, although it can be emulated with constraints like CHECK(typeof(x)='integer').[10] Strict tables were added in version 3.37.1.[22]

Tables normally include a hidden rowid index column, which gives faster access.[24] If a database includes an Integer Primary Key column, SQLite will typically optimize it by treating it as an alias for rowid, causing the contents to be stored as a strictly typed 64-bit signed integer and changing its behavior to be somewhat like an auto-incrementing column. Future[when?] versions of SQLite may include a command to introspect whether a column has behavior like that of rowid to differentiate these columns from weakly typed, non-autoincrementing Integer Primary Keys.[25][failed verification]

Version 3.6.19 released on October 14, 2009 added support for foreign key constraints.[26][27]

Stored procedures are not supported; this is an explicit choice by the developers to favor simplicity, as the typical use case of SQLite is to be embedded inside a host application that can define its own procedures around the database.[28]

Full support for Unicode case-conversions can be enabled through an optional extension.[29]

SQLite version 3.7.4 first saw the addition of the FTS4 (full-text search) module, which features enhancements over the older FTS3 module.[30] FTS4 allows users to perform full-text searches on documents similar to how search engines search webpages.[31] Version 3.8.2 added support for creating tables without rowid,[32] which may provide space and performance improvements.[33] Common table expressions support was added to SQLite in version 3.8.3.[34] 3.8.11 added a newer search module called FTS5, the more radical (compared to FTS4) changes requiring a bump in version.

In 2015, with the json1 extension[35] and new subtype interfaces, SQLite version 3.9 introduced JSON content managing.

As of version 3.33.0, the maximum supported database size is 281 TB.[36]

Development and distribution

[edit]

SQLite's code is hosted with Fossil, a distributed version control system that uses SQLite as a local cache for its non-relational database format, and SQLite's SQL as an implementation language.[37][38]

SQLite is public domain, but not "open-contribution", with the website stating "the project does not accept patches from people who have not submitted an affidavit dedicating their contribution into the public domain."[39] Instead of a code of conduct, the founders have adopted a code of ethics based on the Rule of St. Benedict.[40]

A standalone command-line shell program called sqlite3[41] is provided in SQLite's distribution. It can be used to create a database, define tables, insert and change rows, run queries and manage an SQLite database file. It also serves as an example for writing applications that use the SQLite library.

SQLite uses automated regression testing prior to each release. Over 2 million tests[42] are run as part of a release's verification. Starting with the August 10, 2009 release of SQLite 3.6.17, SQLite releases have 100% branch test coverage, one of the components of code coverage. The tests and test harnesses are partially public-domain and partially proprietary.[42]

Notable uses

[edit]

Operating systems

[edit]

SQLite is included by default in:[11]

Middleware

[edit]
  • ADO.NET adapter, initially developed by Robert Simpson, is maintained jointly with the SQLite developers since April 2010.[44]
  • ODBC driver has been developed and is maintained separately by Christian Werner.[45] Werner's ODBC driver is the recommended connection method for accessing SQLite from OpenOffice.org.[46]
  • COM (ActiveX) wrapper making SQLite accessible on Windows to scripted languages such as JScript and VBScript. This adds SQLite database capabilities to HTML Applications (HTA).[47]

Web browsers

[edit]
  • The browsers Google Chrome, Opera, Safari and the Android Browser all allow for storing information in, and retrieving it from, an SQLite database within the browser, using the official SQLite Wasm (WebAssembly) build,[48] or using the Web SQL Database technology, although the latter is becoming deprecated (namely superseded by SQLite Wasm or by IndexedDB). Internally, these Chromium based browsers use SQLite databases for storing configuration data like site visit history, cookies, download history etc.[49]
  • Mozilla Firefox and Mozilla Thunderbird store a variety of configuration data (bookmarks, cookies, contacts etc.) in internally managed SQLite databases. Until Firefox version 57 ("Firefox Quantum"), there was a third-party add-on that used the API supporting this functionality to provide a user interface for managing arbitrary SQLite databases.[50]
  • Several third-party add-ons can make use of JavaScript APIs to manage SQLite databases.[51][52]

Web application frameworks

[edit]

Others

[edit]

See also

[edit]

References

[edit]

Citations

[edit]
  1. ^ "SQLite Release 3.47.2 On 2024-12-07". Retrieved 8 December 2024.
  2. ^ "SQLite Copyright". sqlite.org. Archived from the original on October 10, 2023. Retrieved May 17, 2010.
  3. ^ "SQLite database file format media type at IANA". Internet Assigned Numbers Authority. IANA. Archived from the original on 2022-11-09. Retrieved 2019-03-08.
  4. ^ "Why SQLite succeeded as a database — Richard Hipp, creator of SQLite". The Changelog. Episode 201. Event occurs at 00:17:25. Archived from the original on 2022-07-07. Retrieved 2019-08-06. How do I pronounce the name of the product? I say S-Q-L-ite, like a mineral.
  5. ^ D. Richard Hipp (presenter) (May 31, 2006). An Introduction to SQLite (video). Google Inc. Event occurs at 00:01:14. Retrieved March 23, 2010. [...] ess-kju-ellite [...]
  6. ^ D. Richard Hipp (presenter) (May 31, 2006). An Introduction to SQLite. Google Inc. Event occurs at 00:48:15. Retrieved March 23, 2010. [...] sequelite [...]
  7. ^ "Most Widely Deployed SQL Database Estimates". SQLite.org. Retrieved May 11, 2011.
  8. ^ Owens, Michael (2006). "Chapter 4: SQL". In Gilmore, Jason; Thomas, Keir (eds.). The Definitive Guide to SQLite. D. Richard Hipp (foreword), Preston Hagar (technical reviewer). Apress. p. 133. ISBN 978-1-59059-673-9. Archived from the original on 24 November 2020. Retrieved 30 December 2014.
  9. ^ "STRICT Tables". Archived from the original on 2022-08-07. Retrieved 2022-08-11.
  10. ^ a b Owens, Michael (2006). The Definitive Guide to SQLite. Apress. doi:10.1007/978-1-4302-0172-4_1. ISBN 978-1-59059-673-9.
  11. ^ a b c "Well-Known Users Of SQLite". SQLite. Archived from the original on July 11, 2015. Retrieved August 5, 2015.
  12. ^ "Interview: Richard Hipp on UnQL, a New Query Language for Document Databases". InfoQ. August 4, 2011. Archived from the original on April 8, 2014. Retrieved October 5, 2011.
  13. ^ McCarthy, Kieren. "SQLite creator crucified after code of conduct warns devs to love God, and not kill, commit adultery, steal, curse..." www.theregister.com. Archived from the original on 2022-11-17. Retrieved 2022-11-17.
  14. ^ "LoC Recommended Storage Format". www.sqlite.org. Archived from the original on 2020-04-23. Retrieved 2020-04-09.
  15. ^ "SQLite, Version 3". www.loc.gov. 2017-03-28. Archived from the original on 2020-05-11. Retrieved 2020-04-09.
  16. ^ "Recommended Formats Statement – datasets/databases". Library of Congress. Archived from the original on 2018-08-22. Retrieved 2020-04-09.
  17. ^ "SQLite Is A Zero-Configuration Database". SQLite.org. Archived from the original on May 2, 2024. Retrieved August 3, 2015.
  18. ^ "Write Ahead Logging in SQLite 3.7". SQLite.org. Archived from the original on May 2, 2024. Retrieved September 3, 2011. WAL provides more concurrency as readers do not block writers and a writer does not block readers. Reading and writing can proceed concurrently.
  19. ^ "Appropriate Uses For SQLite". SQLite.org. Archived from the original on 2024-05-02. Retrieved 2015-09-03.
  20. ^ "PGCon 2014: Clustering and VODKA". Lwn.net. Archived from the original on 2015-06-29. Retrieved 2017-01-06.
  21. ^ "PGCon2014: SQLite: Protégé of PostgreSQL". Pgcon.org. 20 September 2015. Archived from the original on 2014-12-30. Retrieved 2017-01-06.
  22. ^ a b "SQLite: StrictMode". Sqlite.org. Archived from the original on March 4, 2016. Retrieved September 3, 2015.
  23. ^ "Release History of SQLite". Archived from the original on 2021-03-16. Retrieved 2021-03-22.
  24. ^ "SQL As Understood By SQLite". SQLite. Archived from the original on 21 May 2018. Retrieved 21 May 2018. Searching for a record with a specific rowid, or for all records with rowids within a specified range is around twice as fast as a similar search made by specifying any other PRIMARY KEY or indexed value.
  25. ^ "SQLite: Check-in [2494132a]". www.sqlite.org. 2017-11-28. Archived from the original on 2018-05-21. Retrieved 2018-05-21. Add the "PRAGMA table_ipk(TABLE)" command for evaluation purposes.
  26. ^ Karwin, Bill (May 2010). Carter, Jacquelyn (ed.). SQL Antipatterns: Avoiding the Pitfalls of Database Programming. The Pragmatic Bookshelf. p. 70. ISBN 978-1-934356-55-5. Sometimes you're forced to use a database brand that doesn't support foreign key constraints (for example MySQL's MyISAM storage engine or SQLite prior to version 3.6.19).
  27. ^ "SQLite Release 3.6.19 On 2009-10-14". sqlite.org. Archived from the original on 2020-10-29. Retrieved 2020-10-15.
  28. ^ Source: developers' comments on SQLite forum Archived 2023-04-01 at the Wayback Machine
  29. ^ "Case-insensitive matching of Unicode characters does not work". SQLite Frequently Asked Questions. Archived from the original on 2015-09-05. Retrieved 2015-09-03.
  30. ^ "SQLite Release 3.7.4 On 2010-12-08". SQLite.org. December 8, 2010. Archived from the original on September 16, 2015. Retrieved September 3, 2015.
  31. ^ "SQLite FTS3 and FTS4 Extensions". SQLite.org. Archived from the original on September 5, 2015. Retrieved September 3, 2015.
  32. ^ "SQLite Release 3.8.2 On 2013-12-06". SQLite.org. December 6, 2013. Archived from the original on September 24, 2015. Retrieved September 3, 2015.
  33. ^ "The WITHOUT ROWID Optimization". SQLite.org. Archived from the original on September 5, 2015. Retrieved September 3, 2015.
  34. ^ "SQLite Release 3.8.3 On 2014-02-03". SQLite.org. February 3, 2014. Archived from the original on September 5, 2015. Retrieved September 3, 2015.
  35. ^ "The JSON1 Extension". SQLite.org. Archived from the original on 2017-09-14. Retrieved 2017-09-14.
  36. ^ "Limits In SQLite". SQLite.org. Archived from the original on 2021-11-07. Retrieved 2022-09-19.
  37. ^ "Thoughts On The Design Of The Fossil DVCS". Fossil-scm.org. July 12, 2017. Archived from the original on October 13, 2022. Retrieved October 14, 2022.
  38. ^ "Fossil: Fossil Performance". Fossil-scm.org. August 23, 2009. Archived from the original on October 9, 2009. Retrieved September 12, 2009.
  39. ^ "SQLite Copyright". sqlite.org. Archived from the original on 2024-03-15. Retrieved 2024-03-06.
  40. ^ "Code Of Ethics". sqlite.org. Archived from the original on 2024-02-19. Retrieved 2024-03-06.
  41. ^ "Command Line Shell For SQLite". Sqlite.org. Archived from the original on October 6, 2022. Retrieved October 14, 2022.
  42. ^ a b "How SQLite Is Tested". SQLite.org. Archived from the original on October 6, 2009. Retrieved September 12, 2009.
  43. ^ "To use the version of SQLite that is installed with Windows". 20 October 2022. Archived from the original on 31 March 2022. Retrieved 31 March 2022.
  44. ^ "Home". System.Data.SQLite. 2016-12-30. Archived from the original on 2014-07-13. Retrieved 2017-01-06.
  45. ^ "SQLite ODBC Driver". Ch-werner.de. 2016-12-01. Archived from the original on 2014-06-26. Retrieved 2017-01-06.
  46. ^ "Using SQLite Database with OpenOffice.org : Version 2.0" (PDF). Documentation.openoffice.org. Archived (PDF) from the original on 2011-09-28. Retrieved 2017-01-06.
  47. ^ "sqlite — Sqlite Wrappers". SQLite.org. February 7, 2009. Archived from the original on February 5, 2009. Retrieved February 7, 2009.
  48. ^ "sqlite3 WebAssembly & JavaScript Documentation Index". SQLite. Archived from the original on 2024-05-02. Retrieved 2023-05-08.
  49. ^ "Location of Google Chrome history". www.foxtonforensics.com. 2020-10-06. Archived from the original on 2023-02-28. Retrieved 2020-10-06.
  50. ^ "SQLite Manager :: Add-ons for Firefox". Addons.mozilla.org. 2015-02-28. Archived from the original on 2017-01-02. Retrieved 2017-01-06.
  51. ^ "SQLite Manager – Get this Extension for 🦊 Firefox (en-US)". Addons.mozilla.org. 2018-07-24. Archived from the original on 2018-10-05. Retrieved 2018-10-05.
  52. ^ "SQLite Reader – Get this Extension for 🦊 Firefox (en-US)". Addons.mozilla.org. 2018-09-01. Archived from the original on 2018-10-05. Retrieved 2018-10-05.
  53. ^ "Using SQL to find my best photo of a pelican according to Apple Photo". Simon Willison’s Weblog. Archived from the original on May 22, 2020. Retrieved May 23, 2020.
  54. ^ "Audacity 3.0.0 Released". 17 March 2021. Archived from the original on 14 August 2023. Retrieved March 17, 2021.
  55. ^ Hinegardner, Jeremy (August 28, 2007). "Skype client using SQLite?". sqlite-users (Mailing list). Archived from the original on 2007-11-17. Retrieved June 14, 2010.

Sources

[edit]
[edit]