Hi Andrei, Did you get anywhere from here using my feedback? Or do you need more information? I would be very interested to hear more about this problem.
We just had a very peculiar database corruption: the corrupted database (~5Mb) can be accessed from 199 but it appears to be as good as empty. Using 199 to dump the database to an SQL script results in a script with a single CREATE TABLE statement. I used 197 to dump it and got an SQL file of ~17Mb. Importing that got me a working database again, both with 197 and 199. As you can probably sense I am getting a bit nervous about all this. I am still considering reverting to 196 but since that would require me to do a full dump-with-199/import-with-196 cycle for all my databases (somewhere around 10K by now) this would be quite an endeavor. -- You received this message because you are subscribed to the Google Groups "H2 Database" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/h2-database. To view this discussion on the web visit https://groups.google.com/d/msgid/h2-database/05ee049c-8f3e-4a0f-80bf-599580232c8e%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
