I was planning on using the H2 embedded in a client program software
distributed to many workstations. The software off course has to be as
stable as possible, so I get a little worry about the many reports on
corrupted state after OS crash, out of memory, Java crash, program kills
etc. These situations are very expected with normal commodity hardware and
normal users behavior. In my case it is okay to loose data in these
situations, but corrupted state so all data are lost or the application
will not start again is far by good.
I'm using version 1.3.176 and is running single threaded and embedded.
Anything I can do to avoid corrupted state?
Are you planning on improving the old 1.3.176 storage to avoid corrupted
state?
Thanks
Stig
--
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/d/optout.
