Hi, > Usually corruptions arise when disk space is out
With version 1.2.x this should no longer be a problem, because there is only one database file. LOBs could in theory still be a problem, but in practice I rarely hear about problems in this area. Still I am working on a different LOB storage mechanism. > My concern was mainly about durability. Do you mean durability, or that databases don't get corrupt? See also http://www.h2database.com/html/advanced.html#acid - complete durability is hard, but one of the most important features is that databases never get corrupt. With version 1.2.x this problem should be solved (at least I don't know about problems currently). I do run automated power failure tests, and didn't see a problem there lately. > We are using H2 in production > with thousands of installations, > so we would like to have at least some workaround/recipe for our > customers, if something goes wrong and DB is corrupted. If there is a problem, the Recover tool can usually fix the problem. If not (duplicated rows) you may need to manually edit the SQL script. Regards, Thomas -- 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.
