| 1 |
<!DOCTYPE html> |
| 2 |
<html><head> |
| 3 |
<meta name="viewport" content="width=device-width, initial-scale=1.0"> |
| 4 |
<meta http-equiv="content-type" content="text/html; charset=UTF-8"> |
| 5 |
<link href="sqlite.css" rel="stylesheet"> |
| 6 |
<title>Long Term Support</title> |
| 7 |
<!-- path= --> |
| 8 |
</head> |
| 9 |
<body> |
| 10 |
<div class=nosearch> |
| 11 |
<a href="index.html"> |
| 12 |
<img class="logo" src="images/sqlite370_banner.svg" alt="SQLite" border="0"> |
| 13 |
</a> |
| 14 |
<div><!-- IE hack to prevent disappearing logo --></div> |
| 15 |
<div class="tagline desktoponly"> |
| 16 |
Small. Fast. Reliable.<br>Choose any three. |
| 17 |
</div> |
| 18 |
<div class="menu mainmenu"> |
| 19 |
<ul> |
| 20 |
<li><a href="index.html">Home</a> |
| 21 |
<li class='mobileonly'><a href="javascript:void(0)" onclick='toggle_div("submenu")'>Menu</a> |
| 22 |
<li class='wideonly'><a href='about.html'>About</a> |
| 23 |
<li class='desktoponly'><a href="docs.html">Documentation</a> |
| 24 |
<li class='desktoponly'><a href="download.html">Download</a> |
| 25 |
<li class='wideonly'><a href='copyright.html'>License</a> |
| 26 |
<li class='desktoponly'><a href="support.html">Support</a> |
| 27 |
<li class='desktoponly'><a href="prosupport.html">Purchase</a> |
| 28 |
<li class='search' id='search_menubutton'> |
| 29 |
<a href="javascript:void(0)" onclick='toggle_search()'>Search</a> |
| 30 |
</ul> |
| 31 |
</div> |
| 32 |
<div class="menu submenu" id="submenu"> |
| 33 |
<ul> |
| 34 |
<li><a href='about.html'>About</a> |
| 35 |
<li><a href='docs.html'>Documentation</a> |
| 36 |
<li><a href='download.html'>Download</a> |
| 37 |
<li><a href='support.html'>Support</a> |
| 38 |
<li><a href='prosupport.html'>Purchase</a> |
| 39 |
</ul> |
| 40 |
</div> |
| 41 |
<div class="searchmenu" id="searchmenu"> |
| 42 |
<form method="GET" action="search"> |
| 43 |
<select name="s" id="searchtype"> |
| 44 |
<option value="d">Search Documentation</option> |
| 45 |
<option value="c">Search Changelog</option> |
| 46 |
</select> |
| 47 |
<input type="text" name="q" id="searchbox" value=""> |
| 48 |
<input type="submit" value="Go"> |
| 49 |
</form> |
| 50 |
</div> |
| 51 |
</div> |
| 52 |
<script> |
| 53 |
function toggle_div(nm) { |
| 54 |
var w = document.getElementById(nm); |
| 55 |
if( w.style.display=="block" ){ |
| 56 |
w.style.display = "none"; |
| 57 |
}else{ |
| 58 |
w.style.display = "block"; |
| 59 |
} |
| 60 |
} |
| 61 |
function toggle_search() { |
| 62 |
var w = document.getElementById("searchmenu"); |
| 63 |
if( w.style.display=="block" ){ |
| 64 |
w.style.display = "none"; |
| 65 |
} else { |
| 66 |
w.style.display = "block"; |
| 67 |
setTimeout(function(){ |
| 68 |
document.getElementById("searchbox").focus() |
| 69 |
}, 30); |
| 70 |
} |
| 71 |
} |
| 72 |
function div_off(nm){document.getElementById(nm).style.display="none";} |
| 73 |
window.onbeforeunload = function(e){div_off("submenu");} |
| 74 |
/* Disable the Search feature if we are not operating from CGI, since */ |
| 75 |
/* Search is accomplished using CGI and will not work without it. */ |
| 76 |
if( !location.origin || !location.origin.match || !location.origin.match(/http/) ){ |
| 77 |
document.getElementById("search_menubutton").style.display = "none"; |
| 78 |
} |
| 79 |
/* Used by the Hide/Show button beside syntax diagrams, to toggle the */ |
| 80 |
function hideorshow(btn,obj){ |
| 81 |
var x = document.getElementById(obj); |
| 82 |
var b = document.getElementById(btn); |
| 83 |
if( x.style.display!='none' ){ |
| 84 |
x.style.display = 'none'; |
| 85 |
b.innerHTML='show'; |
| 86 |
}else{ |
| 87 |
x.style.display = ''; |
| 88 |
b.innerHTML='hide'; |
| 89 |
} |
| 90 |
return false; |
| 91 |
} |
| 92 |
var antiRobot = 0; |
| 93 |
function antiRobotGo(){ |
| 94 |
if( antiRobot!=3 ) return; |
| 95 |
antiRobot = 7; |
| 96 |
var j = document.getElementById("mtimelink"); |
| 97 |
if(j && j.hasAttribute("data-href")) j.href=j.getAttribute("data-href"); |
| 98 |
} |
| 99 |
function antiRobotDefense(){ |
| 100 |
document.body.onmousedown=function(){ |
| 101 |
antiRobot |= 2; |
| 102 |
antiRobotGo(); |
| 103 |
document.body.onmousedown=null; |
| 104 |
} |
| 105 |
document.body.onmousemove=function(){ |
| 106 |
antiRobot |= 2; |
| 107 |
antiRobotGo(); |
| 108 |
document.body.onmousemove=null; |
| 109 |
} |
| 110 |
setTimeout(function(){ |
| 111 |
antiRobot |= 1; |
| 112 |
antiRobotGo(); |
| 113 |
}, 100) |
| 114 |
antiRobotGo(); |
| 115 |
} |
| 116 |
antiRobotDefense(); |
| 117 |
</script> |
| 118 |
<div class=fancy> |
| 119 |
<div class=nosearch> |
| 120 |
<div class="fancy_title"> |
| 121 |
Long Term Support |
| 122 |
</div> |
| 123 |
</div> |
| 124 |
|
| 125 |
|
| 126 |
|
| 127 |
|
| 128 |
|
| 129 |
<p> |
| 130 |
The intent of the developers is to support SQLite through |
| 131 |
the year 2050. |
| 132 |
|
| 133 |
</p><p> |
| 134 |
At this writing, 2050 is still 25 years in the future. |
| 135 |
Nobody knows what will happen in that time, and we cannot |
| 136 |
absolutely promise that SQLite will be viable or useful that |
| 137 |
far out. |
| 138 |
But we can promise this: we plan as if we will be |
| 139 |
supporting SQLite until 2050. |
| 140 |
That long-term outlook affects our |
| 141 |
decisions in important ways. |
| 142 |
|
| 143 |
</p><ul> |
| 144 |
<li><p> |
| 145 |
<b>Cross-platform Code</b> → |
| 146 |
SQLite runs on any platform with an 8-bit byte, |
| 147 |
two's complement 32-bit and 64-bit integers, |
| 148 |
and a C compiler. It is actively |
| 149 |
tested on all currently popular CPUs and operating |
| 150 |
systems. |
| 151 |
The extreme portability of the SQLite code and file |
| 152 |
format will help it remain viable on future platforms. |
| 153 |
|
| 154 |
</p></li><li><p> |
| 155 |
<b>Stable, Cross-platform Database Files</b> → |
| 156 |
SQLite <a href="fileformat2.html">database files</a> are bit-for-bit identical on |
| 157 |
32-bit, 64-bit, big-endian, and little-endian platforms. You |
| 158 |
can copy an SQLite database file from one system to another |
| 159 |
without having to translate or convert the database. |
| 160 |
Furthermore, the file format is well documented and stable. |
| 161 |
Database files created today will be readable and writable by |
| 162 |
future versions of SQLite decades in the future. |
| 163 |
|
| 164 |
</p></li><li><p> |
| 165 |
<b><a href="testing.html">Aviation-grade testing</a></b> → |
| 166 |
Every machine-code branch instruction is tested in both |
| 167 |
directions. Multiple times. On multiple platforms and with |
| 168 |
multiple compilers. This helps make the code robust for |
| 169 |
future migrations. The intense testing also means that new |
| 170 |
developers can make experimental enhancements to SQLite and, |
| 171 |
assuming legacy tests all pass, be reasonably sure that the |
| 172 |
enhancement does not break legacy. |
| 173 |
|
| 174 |
</p></li><li><p> |
| 175 |
<b>Extensive, detailed documentation</b> → |
| 176 |
SQLite has candid, developer-friendly, |
| 177 |
and open-source documentation. Docs are written by and |
| 178 |
for programmers. |
| 179 |
(A few examples: |
| 180 |
<a href="./arch.html">[1]</a> |
| 181 |
<a href="./fileformat.html">[2]</a> |
| 182 |
<a href="./queryplanner.html">[3]</a> |
| 183 |
<a href="./opcode.html">[4]</a> |
| 184 |
<a href="./compile.html">[5]</a> |
| 185 |
<a href="./malloc.html">[6]</a> |
| 186 |
<a href="./debugging.html">[7]</a> |
| 187 |
<a href="./howtocorrupt.html">[8]</a>) |
| 188 |
The extensive documentation helps new developers |
| 189 |
come up to speed on SQLite very quickly. |
| 190 |
|
| 191 |
</p></li><li><p> |
| 192 |
<b>Heavily commented source code</b> → |
| 193 |
The SQLite source code is over 35% comment. Not boiler-plate |
| 194 |
comments, but useful comments that explain the meaning of variables |
| 195 |
and objects and the intent of methods and procedures. |
| 196 |
The code is designed |
| 197 |
to be accessible to new programmers and maintainable over a span |
| 198 |
of decades. |
| 199 |
|
| 200 |
</p></li><li><p> |
| 201 |
<b>Disaster planning</b> → |
| 202 |
Every byte of source-code history for SQLite is cryptographically |
| 203 |
protected and is automatically replicated to multiple |
| 204 |
geographically separated servers, in datacenters |
| 205 |
owned by different companies. |
| 206 |
Thousands of additional clones exist on private servers around the |
| 207 |
world. |
| 208 |
The primary developers of SQLite live in different regions of the world. |
| 209 |
SQLite can survive a continental catastrophe. |
| 210 |
|
| 211 |
</p></li><li><p> |
| 212 |
<b>Old school</b> → |
| 213 |
Nobody is completely immune to trends and fads, but the SQLite |
| 214 |
developers work hard to avoid being sucked into the latest programming |
| 215 |
fashion. Our aim is to produce timeless code that will be |
| 216 |
readable, understandable, and maintainable by programmers |
| 217 |
who have not yet been born. |
| 218 |
</p></li></ul> |
| 219 |
|
| 220 |
<p> |
| 221 |
In addition to "supporting" SQLite through the year 2050, the developers |
| 222 |
also promise to keep the SQLite |
| 223 |
<a href="cintro.html">C-language API</a> and <a href="fileformat2.html">on-disk format</a> |
| 224 |
fully backwards compatible. |
| 225 |
This means that application written to use SQLite today should be able to |
| 226 |
link against and use future versions of SQLite released decades in the |
| 227 |
future. |
| 228 |
|
| 229 |
</p><p> |
| 230 |
Our goal is to make the content you store in SQLite today as |
| 231 |
easily accessible to your grandchildren as it is to you. |
| 232 |
|
| 233 |
</p><p> |
| 234 |
<b>Update on 2018-05-31:</b> |
| 235 |
Our goal of supporting SQLite long-term have apparently come to the |
| 236 |
notice of the preservationist at the |
| 237 |
<a href="https://www.loc.gov">US Library Of Congress</a> who have identified |
| 238 |
SQLite as a <a href="locrsf.html">recommended storage format</a> for the preservation of |
| 239 |
digital content. |
| 240 |
</p><p align="center"><small><i>This page was last updated on 2025-05-31 13:08:22Z </small></i></p> |
| 241 |
|