Hi, with HSQLDB about once a month I get a user who has a corrupt database, with the previous version this was as high as 3 a month. The main problem by far is when the indexes in the script file do not match the data file. In previous versions this used to throw an IndexOutOfBoundsException but now it can recover from this in some circumstances which is why my corruption rate is less. In the circumstances when it cannot recover it fails silently and the database is just crazy. Indexes are out of sync with the data and fields get junk in them. These problems usually (not always) arise from external causes such as power failures or lock ups but the databases ability to recover from this is imperative.
Any thoughts on this? -Mark On Jan 29, 6:26 pm, Thotheolh <[email protected]> wrote: > Hi. maybe you can state what kind of corruption you are worried that > would occur on H2 which happened on HSQLDB ? > > On Jan 29, 6:57 am, bludginozzie <[email protected]> wrote: > > > > > Hi, > > > I am currently using HSQLDB in a production application and getting > > the occasional report of database corruption. I have had it happen to > > me and the whole database just goes wierd. I am considering a switch > > to H2 but I am concerned that it will suffer the same problems. Has > > anyone had problems with corruption in H2 and/or any thoughts on > > this? aka.. is H2 production ready? > > > Thanks > > > Mark- Hide quoted text - > > - Show quoted text - --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
