Hi John, (01)
I'm not sure how performance compares, but presumably if performance is
your highest priority then you would choose MySQL, Oracle, etc. (02)
Part of the appeal of SQLite and Derby are that they are small,
embeddable, databases. Since SQLite is written in C and Derby is written
in Java, then the choice of which to use may be largely determined by
which language you happen to be coding in. They both run standalone as
well. (03)
SQLite supports multiple language bindings
(http://www.sqlite.org/cvstrac/wiki?p=SqliteWrappers). Derby supports
any client that can talk JDBC, ODBC, or DRDA. (04)
Licenses are open-source friendly. SQLite is in the public domain
(http://www.sqlite.org/copyright.html) so there is no license, and Derby
uses the Apache License v 2.0
(http://www.apache.org/licenses/LICENSE-2.0.html). (05)
SQLite implements most but not all of SQL92 standard.
http://www.sqlite.org/omitted.html (06)
Derby claims compliance with SQL92 and supports some of the SQL99
standard. http://incubator.apache.org/derby/derby_proposal.html (07)
A small wiki page comparing the two is at
http://www.sqlite.org/cvstrac/wiki?p=SqliteVersusDerby (08)
Regards, (09)
Jonathan (010)
John Sechrest wrote:
> How would you compare cloudscape to sqllite?
> (011)
--
This message is archived at: (012)
http://collab.blueoxen.net/forums/cgi-bin/mesg.cgi?a=yak&i=4206D957.7020205@cheyer.biz (013)
|