Jens Stutte wrote:
>
> http://hsql.oron.ch/
>
> However, it is not suitable for larger databases, since the contents is
> stored as sequence of all SQL statements ever made and recalculated on
> restart - which takes quite a while...
> But it's good for exercises or very small projects.
>
This is not completely accurate. If you use "CACHED" tables (in hSql's
terminology), your data is stored on disk (database.data file) as a
random-access, binary file like other SQL databases.
ie: create cached database customers (name char(40), address, varchar);
When using cached tables, only the portion of the database that you use
will be "cached" in memory. So there is no statements to write on disk
when closing the database or to reprocess when opening the database.
So I would rather say that it's suitable for larger databases, but not
for serious mission-critical applications. Although I've seen it being
used in commercial applications.
regards,
alex.
