Check out the documentation.
http://www.h2database.com/html/grammar.html
The meanings of these settings are explained there.
Eg. for LOG=0 it says:
"|LOG| 0 means the transaction log is disabled completely. It is the fastest mode, but also the most dangerous: if the process is killed while the database is open in this mode, the data might be lost. It must only be used if this is not a problem, for example when initially loading a database, or when running tests."

- Rami Ojares

On 29.8.2011 18:52, Hugo wrote:
Ok, I finally got it. The JDBC url was given additionnal parameters,
that somehow prevent the actual flush of the data to the disk, in case
of program crash. Those parameters was:
";CACHE_SIZE=65536;LOCK_MODE=0;LOG=0;UNDO_LOG=0"

I'm not sure which one (or which combination) is the culprit,  nor the
logical reason of such behavior, but at least, if I remove those
parameters everything is going fine.


--
You received this message because you are subscribed to the Google Groups "H2 
Database" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/h2-database?hl=en.

Reply via email to