Hi Silvio, SQL dump / restore is the only supported way to transition from one version to the other. We are making our best trying to preserve compatibility with older db files, but again, it's on a "best effort" basis. Forward compatibility is totaly out of question. And that's I've been talking about released versions. Jumping onto unreleased version is totally "leap of faith", should be no expectations about switching back, or compatibility with future released version. SQL dump/restore should work most of the time though.
On Tuesday, June 13, 2023 at 5:45:10 AM UTC-4 Silvio wrote: > Hello all, > > I created a H2 test build from current trunk. Using this on a bunch of > databases created with 2.1.214 I get the following error on a rather large > part of them: > > org.h2.mvstore.MVStoreException: File is corrupted - unable to recover a > valid set of chunks [2.2.219/6] > > When reverting to 2.1.214 the problem disappears. > > Do databases have to be dumped/restored for this to work properly? Or is > 2.2.219 supposed to be able to use databases created with 2.1.214? > > > -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/h2-database/9fff1b95-1a54-4767-9abb-23c17ebb4ecfn%40googlegroups.com.
