Page History
- 2006-Jul-19 20:55 anonymous
- 2006-Jul-19 16:33 anonymous
- 2006-Jan-17 14:11 anonymous
- 2005-Dec-03 18:22 anonymous
- 2005-Dec-02 14:23 anonymous
- 2005-Dec-02 14:09 anonymous
- 2005-Oct-20 19:56 anonymous
- 2005-Oct-20 19:40 anonymous
- 2005-Oct-20 19:38 anonymous
- 2005-Oct-20 17:27 drh
- 2005-Oct-20 11:21 anonymous
- 2005-Oct-12 17:34 drh
- 2005-Oct-12 17:33 drh
- 2005-Oct-12 10:06 anonymous
- 2005-Oct-12 03:33 anonymous
- 2005-Aug-06 18:18 anonymous
- 2005-Aug-06 14:10 anonymous
- 2005-Aug-04 19:23 drh
Database File
Both database engines keep the entire database (all tables, indices, views, triggers, stored procedures, etc) in a single database file. At this time we have no hard information comparing the file sizes but we suspect they will be similar. SQLite will have a small advantage for the way in stores tables. Firebird will store indices more compactly, on the other hand.
The SQLite database file is cross-platform. Firebird databases cannot be copied between machines with differing byte orders or alignment restrictions. To move a Firebird database between platforms you have to back it up on the old platform then restore it on the new platform.
Engine Footprint
The complete SQLite library is about 230KiB statically linked. The size of Firebird is measured in megabytes.
Features
Both database engines support all the basics of SQL-92: tables, indices, views, triggers, etc. Support in Firebird is more complete. SQLite omits some features.
Speed
Rumors on the web indicate that the speed of both engines is comparible.
To Be Continued...