Editing SQLite (section)

==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" />

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>

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>