Page History
- 2007-Oct-06 16:47 anonymous
- 2006-May-23 09:17 anonymous
- 2006-Mar-05 05:58 anonymous
- 2006-Feb-15 16:20 drh
- 2005-Sep-06 16:39 drh
- 2005-Jun-22 13:06 anonymous
- 2005-Apr-29 08:13 anonymous
- 2005-Apr-29 02:28 anonymous
- 2005-Apr-15 21:19 anonymous
- 2005-Apr-04 22:24 drh
- 2005-Apr-04 22:20 drh
- 2005-Apr-04 22:00 drh
- 2004-Dec-05 21:09 anonymous
- 2004-Nov-05 16:00 anonymous
- 2004-Aug-29 17:10 anonymous
- 2004-Aug-29 16:53 anonymous
- 2004-Aug-14 13:06 drh
- 2004-Aug-04 12:28 anonymous
- 2004-Aug-04 01:18 drh
Zero-Administration
Both SQLite and Derby offer zero-administration, embeddable SQL database engines that store all data in a single cross-platform disk file.
Host Language Support
SQLite is written in ANSI-C. It supports bindings to dozens of language, including Java. Derby is only available to applications written in Java.
SQL Language Support
Derby supports all of SQL92. SQLite only supports a subset of SQL92, though the supported subset is very large.
Executable Size
The footprint of SQLite is less than 250KB. The footprint for Derby is about 2000KB or about 8 time larger.
Concurrency
SQLite allows multiple simultaneous readers and a single writer. Mutiple processes can have the database open simultaneously. Derby only lets a single process open the database at one time.
Crash-Resistance
An SQLite database will survive a program crash or even a power failure. With Derby, if you pull the power plug at the wrong instant, you risk corrupting the database. (Someone please verify this.)
Database File Size
No data is currently available on the relative sizes of the database files for SQLite and Derby.
Speed
No data is currently available on the relative speed of SQLite and Derby database engines.