Hi, Can you please elaborate on this? "Because using version 1.3.176 could have > changed the database file already" >
You use the PageStore storage mechanism. Let's assume there was a bug introduced in H2 version 1.3.176, in the PageStore mechanism. I wouldn't know what that bug could be because there were basically no changes in the PageStore mechanism since a long time, except for a few smaller bugfixes. But let's assume there was a bug that wasn't there before. Now if you have already opened an old database with version 1.3.176, then that might have corrupted the database in some way that is not visible (let's say, a corruption in an index). Now you want to downgrade to a previous version of H2. To do that, I suggest to export the database to a SQL file and re-create it. That will ensure that all possible corruptions are gone. For the same reason it makes sense to upgrade to a new version of H2, and create backups, in the form of SQL scripts, if this is possible, and not in the form of a file copy. > What could be changed by v176 that could cause incompatibilities with v169? It's not about incompatibilities. Regards, Thomas -- 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 http://groups.google.com/group/h2-database. For more options, visit https://groups.google.com/d/optout.
