I don't really understand the behavior of this parameter on the *
Backup.execute* method.

I thought it would disable the possible "log info", but, inspecting the 
code, it goes beyond that.

The problem with the current approach is: if quiet=false, there is an 
attempt to LOCK the database... and the LOCK file remains until the JAVA 
session is terminated... so, another subsequent attempt to BACKUP a **yet 
closed** but now locked database, fails!

-- 
You received this message because you are subscribed to the Google Groups "H2 
Database" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/h2-database.
For more options, visit https://groups.google.com/groups/opt_out.

Reply via email to