Is there some stupid newbie mistake that can cause your Derby databases to 
disappear?

A Derby database is just a filesystem directory, so if you accidentally
remove that directory, you have just removed your database.

Another common source of confusion is to use a relative filesystem name
for a database in your JDBC connection URL, and then change your
current working directory between runs, which causes the relative name
to resolve to a different physical directory, and thus your database
seems to disappear, although in fact it's still present, just in a
different directory than where you're looking.

Lastly, if you're using the brand-new "in-memory" database, then it 
automatically
disappears when you shut the Derby JVM down.

thanks,

bryan

Reply via email to