Documentation Source Text

Artifact Content
Login

Artifact 0c95450eb2cd11a500737d002ee430ca944dcdcc7445a14ed916da5bb7ac0354:


<title>SQLite: Single File Database</title>

<h2>Single-file Cross-platform Database</h2>

<p>
A database in SQLite is a single disk file&sup1.
Furthermore, the [file format] is cross-platform.
A database that is created on one machine can be
copied and used on a different machine with
a different architecture.  SQLite databases
are portable across 32-bit and 64-bit machines
and between 
[http://en.wikipedia.org/wiki/Endianness | big-endian] and 
[http://en.wikipedia.org/wiki/Endianness | little-endian]
architectures.
</p>

<p>
The SQLite database file format is also stable.
All releases of SQLite version 3 can read and write database
files created by the very first SQLite 3 release (version 3.0.0)
going back to 2004-06-18.  This is "backwards compatibility".
The developers promise to maintain backwards compatibility of
the database file format for all future releases of SQLite 3.
"Forwards compatibility" means that older releases
of SQLite can also read and write databases created by newer
releases.  SQLite is usually, but not completely forwards
compatible. 
</p>

<p>
The stability of the SQLite database file format and the fact
that the file format is cross-platform combine to make SQLite
database files an excellent choice as an 
[Application File Format].
The US Library Of Congress acknowledges this by listing SQLite
as a [recommended storage format] for long-term preservation of
digital content.
</p>
</p>

<hr>
<div style='font-size: 75%;'>
<p>Notes:
<ol>
<li>Temporary journal files are created as part of transaction control,
but those extra files are not part of the steady-state database.
</ol>
</div>