Hi, > Could it be the bug in the IntArray that was also listed for 1.1.108 ?
Yes. In any case I suggest to create a backup of the database using SCRIPT TO '...', and then re-create the database using RUNSCRIPT FROM '...'. Regards, Thomas On Fri, Mar 6, 2009 at 10:46 PM, Alex <[email protected]> wrote: > > Thomas, > > We have tried exact same database files with the 1.1.108 JAR and the > problem does not seem to occur. > I don't think that the files were physically corrupt because when we > run these same files with 1.1.107 we did see the problem again. > > Could it be the bug in the IntArray that was also listed for 1.1.108 ? > > Alex > > > On Mar 6, 2:07 pm, Thomas Mueller <[email protected]> > wrote: >> Hi, >> >> Could you re-try with version 1.1.108? One very important bug that was >> fixed is: "When the shutdown hook closed the database, the last log >> file was deleted too early. This could cause uncommitted changes to be >> persisted.". This could have caused the corruption. >> >> 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 -~----------~----~----~----~------~----~------~--~---
