We were mainly looking at the code quality / neatness. But if I remember correctly we identified places where things would not clean up correctly if an exception were thrown. It was a few years back now though, so I don't remember exactly what we discovered.
We did however rescue almost all our data. It turned out it was only one or two records (of millions) which were broken when the driver crashed and refused to read the database. The recovery tool was also useless for us, since it also crashed (or refused to read the file). If I remember correctly we selected all records "surrounding" the faulty ones, and recovered the data that way. /Mikael 2018-05-02 11:08 GMT+02:00 Noel Grandin <noelgran...@gmail.com>: > > > On 2018/05/02 10:48 AM, Mikael Nordenberg wrote: > >> No offence Thomas, but after reading the source code for H2 when we >> investigated our problems, we decided to use a different database. To us, >> it seemed an overwhelming task to get that code in order to make it make it >> stable enough for our needs. >> We switched to Postgres, and all our problems went away. >> >> > Did you identifier any problems in particular? > -- 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 h2-database+unsubscr...@googlegroups.com. To post to this group, send email to h2-database@googlegroups.com. Visit this group at https://groups.google.com/group/h2-database. For more options, visit https://groups.google.com/d/optout.
