Thanks for your reply, Thomas! > I'm not sure if it makes sense to try to find out why your database > (version 1.1.116-1.1.119) got corrupt. If you want to find out, could > you answer the questions below?
I received database corruption some times. Usually corruptions arise when disk space is out but I could not exactly define conditions. I agree with you that it doesn't make sense to analyze corruption state in my old versioned database. So, as a first step we'll try to switch to 1.2 version. Hope that database conversion will go smoothly. >I think that would be dangerous, because the database couldn't know >which one of the row is the correct one. I would rather spend time to >reduce the risk of data corruption than try to better automate >recovery after a crash. My concern was mainly about durability. 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 the problem is still reproduced with the latest H2 versions, we'll provide you with all required data for deeper investigations. Regards, Konstantin -- 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.
