SQLite: Difference between revisions

From Wikipedia, the free encyclopedia
Jump to navigation Jump to search
imported>Great Brightstar
Others: Add Airbus A350 and others, see https://sqlite.org/famous.html
 
imported>AnomieBOT
m Dating maintenance tags: {{Cn}}
 
(2 intermediate revisions by 2 users not shown)
Line 1: Line 1:
{{Short description|Serverless relational database management system}}
{{Short description|Serverless relational database management system}}
{{Infobox software
{{Infobox software
| logo                  = SQLite370.svg
| logo                  = SQLite370.svg
Line 24: Line 23:
| website                = {{Official URL}}
| website                = {{Official URL}}
}}
}}
{{Infobox file format
{{Infobox file format
| name          = SQLite Database File Format
| name          = SQLite Database File Format
Line 46: Line 44:
| standard      =  
| standard      =  
| open          = yes ([[Public Domain]])
| open          = yes ([[Public Domain]])
| url          = {{url|https://sqlite.org/fileformat.html}}
| url          = {{URL|https://sqlite.org/fileformat.html}}
}}
}}


'''SQLite''' ({{IPAc-en|ˌ|ɛ|s|ˌ|k|juː|ˌ|ɛ|l|ˈ|aɪ|t}} "S-Q-L-ite",<ref>{{cite episode |series=The Changelog |number=201 |title=Why SQLite succeeded as a database — Richard Hipp, creator of SQLite |time=00:16:00 |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=2025-04-11 |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={{IPA|[ˌɛsˌkjuˌwəlˈaɪt̚]}}}}</ref> {{IPAc-en|ˈ|s|iː|k|w|ə|,|l|aɪ|t}} "sequel-ite"<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={{IPA|[ˈsikwəˌlaɪt̚]}} }}</ref>) is a [[Free and open-source software|free and open-source]] [[Relational database|relational]] [[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}} "S-Q-L-ite",<ref>{{cite episode |series=The Changelog |number=201 |title=Why SQLite succeeded as a database — Richard Hipp, creator of SQLite |time=00:16:00 |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=2025-04-11 |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={{IPA|[ˌɛsˌkjuˌwəlˈaɪt̚]}}}}</ref> {{IPAc-en|ˈ|s|iː|k|w|ə|,|l|aɪ|t}} "sequel-ite"<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={{IPA|[ˈsikwəˌlaɪt̚]}} }}</ref>) is a [[Free and open-source software|free and open-source]] [[Relational database|relational]] [[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. According to its developers, SQLite is the most widely deployed database engine, as it is used by several of the top [[web browser]]s, [[operating system]]s, [[mobile phone]]s, 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 |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://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://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. Although it is a lightweight embedded database, SQLite implements most of the [[SQL]] standard and the [[relational model]], including [[Transaction processing|transactions]] and [[ACID]] guarantees.<ref>{{Cite web |title=Full-Featured SQL |url=https://www.sqlite.org/fullsql.html |access-date=January 24, 2025 |website=SQLite}}</ref> However, it omits many features implemented by other databases, such as [[Materialized view|materialized views]] and complete support for [[Database trigger|triggers]] and [[SQL syntax|ALTER TABLE statements]].<ref>{{Cite web |title=SQL Features That SQLite Does Not Implement |url=https://www.sqlite.org/omitted.html |access-date=January 24, 2025 |website=SQLite}}</ref>
Many [[programming language]]s 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://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://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. Although it is a lightweight embedded database, SQLite implements most of the [[SQL]] standard and the [[relational model]], including [[Transaction processing|transactions]] and [[ACID]] guarantees.<ref>{{Cite web |title=Full-Featured SQL |url=https://www.sqlite.org/fullsql.html |access-date=January 24, 2025 |website=SQLite}}</ref> However, it omits many features implemented by other databases, such as [[materialized view]]s and complete support for [[Database trigger|triggers]] and [[SQL syntax|ALTER TABLE statements]].<ref>{{Cite web |title=SQL Features That SQLite Does Not Implement |url=https://www.sqlite.org/omitted.html |access-date=January 24, 2025 |website=SQLite}}</ref>


==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 |chapter=Introducing 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|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 |chapter=Introducing SQLite |year=2006 |pages=1–16 |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|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, 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|Code of Conduct]] because some clients would not use the software without one.<ref>{{Cite web |last=Hipp |first=D. Richard |title=Code of Ethics |url=https://sqlite.org/codeofethics.html |access-date=January 24, 2025 |website=SQLite}}</ref> It was based on the [[Rule of Saint Benedict]] and was controversial for its religious nature. The document 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>
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,{{efn|SQLite's B-tree implementation was originally adapted from [[The Art of Computer Programming]].<ref>{{cite web |last1=Bell |first1=Adam |title=The Untold Story of SQLite |url=https://corecursive.com/066-sqlite-with-richard-hipp/ |website=Corecursive |access-date=16 November 2025}}</ref>}} 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>


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://sqlite.org/locrsf.html |title=LoC Recommended Storage Format |website=sqlite.org |access-date=2020-04-09 |archive-date=2020-04-23 |archive-url=https://web.archive.org/web/20200423212849/https://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>
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://sqlite.org/locrsf.html |title=LoC Recommended Storage Format |website=sqlite.org |access-date=2020-04-09 |archive-date=2020-04-23 |archive-url=https://web.archive.org/web/20200423212849/https://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>
Line 69: Line 65:
SQLite stores the entire database, consisting of definitions, [[Table (database)|tables]], indices, and data, as a single [[Cross-platform software|cross-platform]] file, 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.<ref name=":2" /> 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 stores the entire database, consisting of definitions, [[Table (database)|tables]], indices, and data, as a single [[Cross-platform software|cross-platform]] file, 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.<ref name=":2" /> 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 |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">{{cite web |title=SQLite: StrictMode |url=https://sqlite.org/src/wiki?name=StrictMode |url-status=live |archive-url=https://web.archive.org/web/20160304115940/https://sqlite.org/src/wiki?name=StrictMode |archive-date=March 4, 2016 |access-date=September 3, 2015 |website=Sqlite.org}}</ref>
SQLite uses [[PostgreSQL]] as a reference platform. "What would PostgreSQL do" is used to make sense of the SQL standard.<ref>{{cite web |last1=Berkus |first1=Josh |url=https://lwn.net/Articles/601144/ |title=PGCon 2014: Clustering and VODKA |website=Lwn.net |date=4 June 2014 |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">{{cite web |title=SQLite: StrictMode |url=https://sqlite.org/src/wiki?name=StrictMode |url-status=live |archive-url=https://web.archive.org/web/20160304115940/https://sqlite.org/src/wiki?name=StrictMode |archive-date=March 4, 2016 |access-date=September 3, 2015 |website=Sqlite.org}}</ref>


==Features==
==Features==
Line 87: Line 83:


SQLite includes support for working with [[JSON]] through its ''json1'' extension, which is enabled by default since 2021. SQLite's JSON functions can handle JSON5 syntax since 2023. In 2024, SQLite added support for JSONB, a binary serialization of SQLite's internal representation of JSON. Using JSONB allows applications to avoid having to parse the JSON text each time it is processed and saves a small amount of disk space.<ref>{{Cite web |title=JSON Functions And Operators |url=https://sqlite.org/json1.html |access-date=January 24, 2025 |website=SQLite}}</ref>
SQLite includes support for working with [[JSON]] through its ''json1'' extension, which is enabled by default since 2021. SQLite's JSON functions can handle JSON5 syntax since 2023. In 2024, SQLite added support for JSONB, a binary serialization of SQLite's internal representation of JSON. Using JSONB allows applications to avoid having to parse the JSON text each time it is processed and saves a small amount of disk space.<ref>{{Cite web |title=JSON Functions And Operators |url=https://sqlite.org/json1.html |access-date=January 24, 2025 |website=SQLite}}</ref>
In May 2025, the 25th‑anniversary release SQLite 3.50.0 introduced additional features, including new Unicode functions ({{Code|unistr()}} and {{Code|unistr_quote()}}), a new API ({{Code|sqlite3_setlk_timeout()}}) for setting lock timeouts, improved command‑line tools and rsync utility enhancements, and optimized JSONB.<ref>{{Cite web |title=SQLite Release 3.50.0 On 2025-05-29 |url=https://sqlite.org/releaselog/3_50_0.html |access-date=November 3, 2025 |website=SQLite}}</ref>


The maximum supported size for an SQLite database file is 281 terabytes.<ref>{{cite web|url=https://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>
The maximum supported size for an SQLite database file is 281 terabytes.<ref>{{cite web|url=https://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>
Line 93: Line 91:
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'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://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>  
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://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://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://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.
A standalone [[Console application|command-line]] [[Shell (computing)|shell]] program called ''sqlite3''<ref>{{cite web|url = https://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://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 are run as part of a release's verification. The SQLite library has 156,000 lines of source code, while all the test suites combined add up to 92 million lines of test code. SQLite's tests simulate a number of exceptional scenarios, such as power loss and I/O errors, in addition to testing the library's functionality. 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]]. SQLite has four different [[Test harness|test harnesses]]: the original public-domain TCL tests, the proprietary C-language TH3 test suite, the SQL Logic Tests, which check SQLite against other SQL databases, and the dbsqlfuzz proprietary [[fuzzing]] engine.<ref name="tests">{{cite web |title=How SQLite Is Tested |url=https://sqlite.org/testing.html |url-status=live |archive-url=https://web.archive.org/web/20091006224147/https://sqlite.org/testing.html |archive-date=October 6, 2009 |access-date=September 12, 2009 |publisher=SQLite.org}}</ref>
SQLite uses automated [[regression testing]] prior to each release. Over 2 million tests are run as part of a release's verification. The SQLite library has 156,000 lines of source code, while all the test suites combined add up to 92 million lines of test code. SQLite's tests simulate a number of exceptional scenarios, such as power loss and I/O errors, in addition to testing the library's functionality. 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]]. SQLite has four different [[test harness]]es: the original public-domain TCL tests, the proprietary C-language TH3 test suite, the SQL Logic Tests, which check SQLite against other SQL databases, and the dbsqlfuzz proprietary [[fuzzing]] engine.<ref name="tests">{{cite web |title=How SQLite Is Tested |url=https://sqlite.org/testing.html |url-status=live |archive-url=https://web.archive.org/web/20091006224147/https://sqlite.org/testing.html |archive-date=October 6, 2009 |access-date=September 12, 2009 |publisher=SQLite.org}}</ref>


=={{anchor|Adoption}}Notable uses==
=={{anchor|Adoption}}Notable uses==


===Operating systems===
===Operating systems===
SQLite is included by default in:<ref name=":0" />
SQLite is included by default in:
* [[Android (operating system)|Android]]
* [[Android (operating system)|Android]]{{cn|date=December 2025}}
* [[BlackBerry 10]] OS
* [[BlackBerry 10]] OS{{cn|date=December 2025}}
* [[Fedora Linux]] where it is used by the [[RPM Package Manager|rpm]] core package management system
* [[Fedora Linux]] where it is used by the [[RPM Package Manager|rpm]] core package management system{{cn|date=December 2025}}
* [[FreeBSD]] where starting with 10-RELEASE version in January 2014, it is used by the core package management system.
* [[FreeBSD]] where starting with 10-RELEASE version in January 2014, it is used by the core package management system.{{cn|date=December 2025}}
* [[illumos]]
* [[illumos]]{{cn|date=December 2025}}
* [[iOS]]
* [[iOS]]<ref name=":0" />
* [[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)<ref name=":0" />
* [[Maemo]]
* [[Maemo]]{{cn|date=December 2025}}
* [[MeeGo]]
* [[MeeGo]]{{cn|date=December 2025}}
* [[MorphOS]] 3.10 onwards
* [[MorphOS]] 3.10 onwards{{cn|date=December 2025}}
* [[NetBSD]]
* [[NetBSD]]{{cn|date=December 2025}}
* [[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{{cn|date=December 2025}}
* [[Red Hat Enterprise Linux]] where it is used in the same way as Fedora, from which Red Hat Enterprise Linux is derived
* [[Red Hat Enterprise Linux]] where it is used in the same way as Fedora, from which Red Hat Enterprise Linux is derived{{cn|date=December 2025}}
* [[Solaris 10]] where the [[Service Management Facility]] database is serialized for booting.
* [[Solaris 10]] where the [[Service Management Facility]] database is serialized for booting.{{cn|date=December 2025}}
* [[Symbian OS]]
* [[Symbian OS]]{{cn|date=December 2025}}
* [[Tizen]]
* [[Tizen]]{{cn|date=December 2025}}
* [[webOS]]
* [[webOS]]{{cn|date=December 2025}}
* [[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>
* [[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>


Line 149: Line 147:
* [[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===
Line 157: Line 154:
* [[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>
* [[WhatsApp]]<ref name="WhatsApp">{{cite web |title=WhatsApp in Plain Sight: Where and How You Can Collect Forensic Artifacts |url=https://www.group-ib.com/blog/whatsapp-forensic-artifacts/ |website=www.group-ib.com |access-date=29 September 2025 |date=7 November 2019}}</ref>
* The Service Management Facility, used for service management within the [[Solaris (operating system)|Solaris]] and [[OpenSolaris]] operating systems
* The Service Management Facility, used for service management within the [[Solaris (operating system)|Solaris]] and [[OpenSolaris]] operating systems
* [[Dropbox]] client software<ref name=":0"/>
* [[Intuit]] uses SQLite in [[QuickBooks]] and [[TurboTax]]<ref name=":0"/>
* [[McAfee Antivirus]]<ref name=":0"/>
* [[Flame (malware)]]
* [[Flame (malware)]]
* [[BMW]] [[IDrive]] Sat Nav system
* [[BMW iDrive]] [[satellite navigation]] 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])
* [[Proxmox Virtual Environment|Proxmox VE]] - ''Proxmox Cluster File System'' ([https://pve.proxmox.com/wiki/Proxmox_Cluster_File_System_(pmxcfs) pmxcfs])
* [[Bentley Systems]] MicroStation<ref name=":0"/>
* [[Bentley Systems]] [[MicroStation]]<ref name=":0"/>
* [[Bosch (company)|Bosch]] car multimedia systems <ref name=":0"/>
* [[Bosch (company)|Bosch]] car multimedia systems<ref name=":0"/>
* [[Airbus A350]] flight system<ref name=":0"/>
* [[Airbus A350]] flight system<ref name=":0"/>
* [[Quicken#History of Quicken on Mac|Quicken Essentials]] and later versions of Quicken for Mac<ref>{{cite web|url=https://frugalvagabond.com/addendum-project-years-of-expenses-with-quicken-for-mac/|title=Addendum: Project Years of Expenses With Quicken for Mac|website=The Frugal Vagabond}}</ref>
* [[Python (programming language)|Python]] standard library<ref>{{Cite web
| url = https://docs.python.org/library/sqlite3
| title = sqlite3 — DB-API 2.0 interface for SQLite databases
| website = The Python Standard Library Documentation
}}</ref>
* [[Xojo]] IDE<ref name=":0"/>


==See also==
==See also==
{{Portal|Free and open-source software}}
{{Portal|Free and open-source software}}
* [[Ordered key–value store]]
* [[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]]
* [[MySQL]]
* [[SpatiaLite]]
* [[SpatiaLite]]
==Notes==
{{Notelist}}


==References==
==References==
Line 228: Line 240:
}}
}}
{{Refend}}
{{Refend}}
==Further reading==
* {{cite journal |journal=Proceedings of the VLDB Endowment |url=https://dl.acm.org/doi/10.14778/3554821.3554842 |doi=10.14778/3554821.3554842 |title=SQLite: past, present, and future |date=2022-08-01 |volume=15 |number=12 |pages=3535–3547 |first1=Kevin P |last1=Gaffney |first2=Martin |last2=Prammer |first3=Larry |last3=Brasfield |first4=D Richard |last4=Hipp |first5=Dan |last5=Kennedy |first6=Jignesh M |last6=Patel|url-access=subscription }}


==External links==
==External links==

Latest revision as of 20:34, 30 December 2025

Template:Short description Script error: No such module "Infobox".Template:Template other Script error: No such module "Check for unknown parameters".Script error: No such module "Check for conflicting parameters". Script error: No such module "Infobox".Template:Template otherScript error: No such module "Check for unknown parameters".

SQLite (Template:IPAc-en "S-Q-L-ite",[1][2] Template:IPAc-en "sequel-ite"[3]) is a free and open-source relational 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. According to its developers, SQLite 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.[4]

Many programming languages have bindings to the SQLite library. It generally follows PostgreSQL syntax, but does not enforce type checking by default.[5][6] This means that one can, for example, insert a string into a column defined as an integer. Although it is a lightweight embedded database, SQLite implements most of the SQL standard and the relational model, including transactions and ACID guarantees.[7] However, it omits many features implemented by other databases, such as materialized views and complete support for triggers and ALTER TABLE statements.[8]

History

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

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,Template:Efn 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.[11]

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

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 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-configuration[15] because configuration tasks such as service management, startup scripts, and password- or GRANT-based access control are unnecessary. Access control is handled through the file-system permissions of the database file.[16] 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 entire database, consisting of definitions, tables, indices, and data, as a single cross-platform file, allowing several processes or threads to access the same database concurrently. It implements this simple design by locking the database file during writing.[16] 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.[17] Since SQLite has to rely on file-system locks, it is not the preferred choice for write-intensive deployments.[18]

SQLite uses PostgreSQL as a reference platform. "What would PostgreSQL do" is used to make sense of the SQL standard.[19][20] 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.[21]

Features

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.[22]

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').[9] In 2021, support for static typing was added through STRICT tables, which enforce datatype constraints for columns.[23]

Tables normally include a hidden rowid index column, which provides faster access.[24] If a table includes an INTEGER PRIMARY KEY column, SQLite will typically optimize it by treating it as an alias for the 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. SQLite includes an option to create a table without a rowid column, which can save disk space and improve lookup speed. WITHOUT ROWID tables are required to have a primary key.[25]

SQLite supports foreign key constraints,[26][27] although they are disabled by default and must be manually enabled with a PRAGMA statement.[28]

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.[29]

SQLite does not have full Unicode support by default for backwards compatibility and due to the size of the Unicode tables, which are larger than the SQLite library.[30] Full support for Unicode case-conversions can be enabled through an optional extension.[31]

SQLite supports full-text search through its FTS5 loadable extension, which allows users to efficiently search for a keyword in a large number of documents similar to how search engines search webpages.[32]

SQLite includes support for working with JSON through its json1 extension, which is enabled by default since 2021. SQLite's JSON functions can handle JSON5 syntax since 2023. In 2024, SQLite added support for JSONB, a binary serialization of SQLite's internal representation of JSON. Using JSONB allows applications to avoid having to parse the JSON text each time it is processed and saves a small amount of disk space.[33]

In May 2025, the 25th‑anniversary release SQLite 3.50.0 introduced additional features, including new Unicode functions (unistr() and unistr_quote()), a new API (sqlite3_setlk_timeout()) for setting lock timeouts, improved command‑line tools and rsync utility enhancements, and optimized JSONB.[34]

The maximum supported size for an SQLite database file is 281 terabytes.[35]

Development and distribution

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.[36][37]

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."[38] Instead of a code of conduct, the founders have adopted a code of ethics based on the Rule of St. Benedict.[39]

A standalone command-line shell program called sqlite3[40] 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 are run as part of a release's verification. The SQLite library has 156,000 lines of source code, while all the test suites combined add up to 92 million lines of test code. SQLite's tests simulate a number of exceptional scenarios, such as power loss and I/O errors, in addition to testing the library's functionality. 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. SQLite has four different test harnesses: the original public-domain TCL tests, the proprietary C-language TH3 test suite, the SQL Logic Tests, which check SQLite against other SQL databases, and the dbsqlfuzz proprietary fuzzing engine.[41]

Script error: No such module "anchor".Notable uses

Operating systems

SQLite is included by default in:

  • AndroidScript error: No such module "Unsubst".
  • BlackBerry 10 OSScript error: No such module "Unsubst".
  • Fedora Linux where it is used by the rpm core package management systemScript error: No such module "Unsubst".
  • FreeBSD where starting with 10-RELEASE version in January 2014, it is used by the core package management system.Script error: No such module "Unsubst".
  • illumosScript error: No such module "Unsubst".
  • iOS[10]
  • Mac OS X 10.4 onwards (Apple adopted it as an option in macOS's Core Data API from the original implementation)[10]
  • MaemoScript error: No such module "Unsubst".
  • MeeGoScript error: No such module "Unsubst".
  • MorphOS 3.10 onwardsScript error: No such module "Unsubst".
  • NetBSDScript error: No such module "Unsubst".
  • NixOS where it is used by the Nix core package management systemScript error: No such module "Unsubst".
  • Red Hat Enterprise Linux where it is used in the same way as Fedora, from which Red Hat Enterprise Linux is derivedScript error: No such module "Unsubst".
  • Solaris 10 where the Service Management Facility database is serialized for booting.Script error: No such module "Unsubst".
  • Symbian OSScript error: No such module "Unsubst".
  • TizenScript error: No such module "Unsubst".
  • webOSScript error: No such module "Unsubst".
  • Windows 10 onwards[42]

Middleware

  • ADO.NET adapter, initially developed by Robert Simpson, is maintained jointly with the SQLite developers since April 2010.[43]
  • ODBC driver has been developed and is maintained separately by Christian Werner.[44] Werner's ODBC driver is the recommended connection method for accessing SQLite from OpenOffice.org.[45]
  • 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).[46]

Web browsers

  • 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,[47] 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.[48]
  • 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.[49]
  • Several third-party add-ons can make use of JavaScript APIs to manage SQLite databases.[50][51]

Web application frameworks

Others

See also

Script error: No such module "Portal".

Notes

Template:Notelist

References

Citations

<templatestyles src="Reflist/styles.css" />

  1. Script error: No such module "citation/CS1".
  2. Template:Cite video
  3. Template:Cite video
  4. Script error: No such module "citation/CS1".
  5. Script error: No such module "citation/CS1".
  6. Script error: No such module "citation/CS1".
  7. Script error: No such module "citation/CS1".
  8. Script error: No such module "citation/CS1".
  9. a b Script error: No such module "citation/CS1".
  10. a b c d e f g h i j k Script error: No such module "citation/CS1".
  11. Script error: No such module "citation/CS1".
  12. Script error: No such module "citation/CS1".
  13. Script error: No such module "citation/CS1".
  14. Script error: No such module "citation/CS1".
  15. Script error: No such module "citation/CS1".
  16. a b Script error: No such module "citation/CS1".
  17. Script error: No such module "citation/CS1".
  18. Script error: No such module "citation/CS1".
  19. Script error: No such module "citation/CS1".
  20. Script error: No such module "citation/CS1".
  21. Script error: No such module "citation/CS1".
  22. Script error: No such module "citation/CS1".
  23. Script error: No such module "citation/CS1".
  24. Script error: No such module "citation/CS1".
  25. Script error: No such module "citation/CS1".
  26. Script error: No such module "citation/CS1".
  27. Script error: No such module "citation/CS1".
  28. Script error: No such module "citation/CS1".
  29. Source: developers' comments on SQLite forum Template:Webarchive
  30. Script error: No such module "citation/CS1".
  31. Script error: No such module "citation/CS1".
  32. Script error: No such module "citation/CS1".
  33. Script error: No such module "citation/CS1".
  34. Script error: No such module "citation/CS1".
  35. Script error: No such module "citation/CS1".
  36. Script error: No such module "citation/CS1".
  37. Script error: No such module "citation/CS1".
  38. Script error: No such module "citation/CS1".
  39. Script error: No such module "citation/CS1".
  40. Script error: No such module "citation/CS1".
  41. Script error: No such module "citation/CS1".
  42. Script error: No such module "citation/CS1".
  43. Script error: No such module "citation/CS1".
  44. Script error: No such module "citation/CS1".
  45. Script error: No such module "citation/CS1".
  46. Script error: No such module "citation/CS1".
  47. Script error: No such module "citation/CS1".
  48. Script error: No such module "citation/CS1".
  49. Script error: No such module "citation/CS1".
  50. Script error: No such module "citation/CS1".
  51. Script error: No such module "citation/CS1".
  52. Script error: No such module "citation/CS1".
  53. Script error: No such module "citation/CS1".
  54. Script error: No such module "citation/CS1".
  55. Script error: No such module "citation/CS1".
  56. Script error: No such module "citation/CS1".
  57. Script error: No such module "citation/CS1".

Script error: No such module "Check for unknown parameters".

Sources

<templatestyles src="Refbegin/styles.css" />

  • Script error: No such module "citation/CS1".
  • Script error: No such module "citation/CS1".
  • Script error: No such module "citation/CS1".

Further reading

  • Script error: No such module "Citation/CS1".

External links

Template:Sister project

  • Script error: No such module "Official website".Script error: No such module "Check for unknown parameters".
  • Script error: No such module "citation/CS1".

Template:Authority control