Hi, > I hand correct the data to get the database reloaded.
Yes, I'm afraid this is the only solution for this case. > That implies the database was corrupted but it would be handy if the > recover tool could generate clean SQL commands and ignore bad data. Database file should never get corrupt, even if the process is killed while writing. Unfortunately it turned out there were still some bugs up to version 1.2.134. Actually, database files should not get corrupt even on power failure, but so far I don't have enough test cases to verify this (I do test it from time to time, in the past with FAT32 and NTFS and currently with Ext2, but it would be much better to test with many files system). 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.
