Artifact 051086bc273a36808dc08d58ed098611fb53e315:
- File
www/different.tcl
— part of check-in
[38401dfb]
at
2005-01-20 22:48:48
on branch trunk
— Bug fixes and enhancements entered while on jury recess. (CVS 2246)
(user:
drh
size: 6025)
set rcsid {$Id: different.tcl,v 1.2 2005/01/20 22:48:49 drh Exp $}
source common.tcl
header {Distinctive Features Of SQLite}
puts {
<p>
This page highlights some of the characteristics of SQLite that are
unusual and which make SQLite different from many other SQL
database engines.
</p>
}
proc feature {tag name text} {
puts "<a name=\"$tag\" />"
puts "<p><b>$name</b></p>\n"
puts "<blockquote>$text</blockquote>\n"
}
feature zeroconfig {Zero-Configuration} {
SQLite does not need to be "installed" before it is used.
There is no "setup" procedure. There is no
server process that needs to be started, stopped, or configured.
There is
no need for an administrator to create a new database instance or assign
access permissions to users.
SQLite uses no configuration files.
Nothing needs to be done to tell the system that SQLite is running.
No actions are required to recover after a system crash or power failure.
There is nothing to troubleshoot.
<p>
SQLite just works.
<p>
Other more familiar database engines run great once you get them going.
But doing the initial installation and configuration can be
intimidatingly complex.
}
feature serverless {Serverless} {
Most SQL database engines are implemented as a separate server
process. Programs that want to access the database communicate
with the server using some kind of interprocess communcation
(typically TCP/IP) to send requests to the server and to receive
back results. SQLite does not work this way. With SQLite, the
process that wants to access the database reads and writes
directly from the database files on disk. There is no intermediary
server process.
<p>
There are advantages and disadvantages to being serverless. The
main advantage is that there is no separate server process
to install, setup, configure, initialize, manage, and troubleshoot.
This is one reason why SQLite is a "zero-configuration" database
engine. Programs that use SQLite require no administrative support
for setting up the database engine before they are run. Any program
that is able to access the disk is able to use an SQLite database.
<p>
On the other hand, a database engine that uses a server can provide
better protection from bugs in the client application - stray pointers
in a client cannot corrupt memory on the server. And because a server
is a single persistent process, it is able control database access with
more precision, allowing for finer grain locking and better concurrancy.
<p>
Most SQL database engines are client/server based. Of those that are
serverless, SQLite is the only one that this author knows of that
allows multiple applications to access the same database at the same time.
}
feature onefile {Single Database File} {
An SQLite database is a single ordinary disk file that can be located
anywhere in the directory hierarchy. If SQLite can read
the disk file then it can read anything in the database. If the disk
file and its directory are writable, then SQLite can change anything
in the database. Database files can easily be copied onto a USB
memory stick or emailed for sharing.
<p>
Other SQL database engines tend to store data as a large collection of
files. Often these files are in a standard location that only the
database engine itself can access. This makes the data more secure,
but also makes it harder to access. Some SQL database engines provide
the option of writing directly to disk and bypassing the filesystem
all together. This provides added performance, but at the cost of
considerable setup and maintenance complexity.
}
feature small {Compact} {
When optimized for size, the whole SQLite library with everything enabled
is less than 220KiB in size (as measured on an ix86 using the "size"
utility from the GNU compiler suite.) Unneeded features can be disabled
at compile-time to further reduce the size of the library to under
170KiB if desired.
<p>
Most other SQL database engines are much larger than this. IBM boasts
that it's recently released CloudScape database engine is "only" a 2MiB
jar file - 10 times larger than SQLite even after it is compressed!
Firefox boasts that it's client-side library is only 350KiB. That's
50% larger than SQLite and does not even contain the database engine.
The Berkeley DB library from Sleepycat is 450KiB and it lacks a schema
layer.
}
feature typing {Manifest typing} {
}
feature readable {Readable source code} {
}
feature vdbe {SQL statements compile into virtual machine code} {
}
feature binding {Tight bindings to dynamic languages} {
}
feature license {Public domain} {
The source code for SQLite is in the public domain. No claim of copyright
is made on any part of the core source code. (The documentation and test
code is a different matter - some sections of documentation and test logic
are governed by open-sources licenses.) All contributors to the
SQLite core software have signed releases specifically disavowing any
copyright interest in the code. This means that anybody is able to legally
do anything they want with the SQLite source code.
<p>
There are other SQL database engines with liberal licenses that allow
the code to be broadly and freely used. But those other engines are
still governed by copyright law. SQLite is different in that copyright
law simply does not apply.
<p>
The source code files for other SQL database engines typically begin
with a comment describing your license rights to view and copy that file.
The SQLite source code contains no license since it is not governed by
copyright. Instead of a license, the SQLite source code offers a blessing:
<blockquote>
<i>May you do good and not evil<br>
May you find forgiveness for yourself and forgive others<br>
May you share freely, never taking more than you give.</i>
</blockquote>
}
feature extensions {SQL language extensions} {
}
footer $rcsid