Michael Segel wrote:
On Wednesday 14 December 2005 2:42 am, Roger Keays wrote:
I saw on the derby todo list[0] that there were plans to store a derby
[...]
That would be highly inefficient and wouldn't scale.
Why SQLite does this ( http://sqlite.org/ )
and is very fast. May be faster than Derby.
Application users are used to having a single
file manage a 'set of work'. Eg. a PSD file
for work with an image, or a XLS, or DOC file
etc.
If a developer uses Derby for storage this
would get cumbersome. Zipping the derby DB
directory is one approach, but that
complicates application saves, crash recovery,
etc.
Regards,
Kervin
