Mark Hiles wrote:
I've just started using Derby for a uni project and have a couple of
quick questions.
When creating an embedded database, it seems to get overridden each
time I run my application. How can I make it create a database the
first time it runs, and then re-use it in the future?
This is actually what will happen if your connection URL contains
"create=true". If the DB already exists, you will get a connection to
the existing DB.
I'd also like to know if it's possible to select certain data for
archiving / compression? I've searched for material but can't find
anything.
It is possible to encrypt data on disk, but I do not think compression
is supported.
--
Øystein
