SQLite CVSTrac

*** 18,29 ****
  
  *Zero-Administration*
  
! Both SQLite and Derby offer zero-administration, embeddable SQL database engines. SQLite stores all the data in a single cross-platform disk files, wheras Derby uses several files.
  
  *Host Language Support*
  
  SQLite is written in ANSI-C.  It supports bindings to dozens of language,
! including Java.  Derby is written in Java, provides JDBC access, local access (embedded) or remote access (tcpip), using JDBC, DRDA or ODBC drivers.
  
  *SQL Language Support*
  
--- 18,31 ----
  
  *Zero-Administration*
  
! Both SQLite and Derby offer zero-administration, embeddable SQL database engines. SQLite stores all the data in a single cross-platform disk file.
! Derby spreads its data across multiple disk files.
  
  *Host Language Support*
  
  SQLite is written in ANSI-C.  It supports bindings to dozens of language,
! including Java.  Derby is written in Java and is thus usable by Java
! programs only.
  
  *SQL Language Support*
  
***************
*** 34,40 ****
  *Memory Utilization*
  
  The code footprint of SQLite is less than 250KB.  The code footprint for Derby
! is about 2000KB or about 8 time larger.
  
  *Concurrency*
  
--- 36,44 ----
  *Memory Utilization*
  
  The code footprint of SQLite is less than 250KB.  The code footprint for Derby
! is about 2000KB compressed and is thus more than 8 time larger.
! 
! No information is available on the run-time memory utilization of Derby.
  
  *Concurrency*

sqlite - Sqlite Versus Derby