Nice explanation! Thanks. I believe this is not the case, as i made several tests before downgrading.
Anyway, backups are already implemented everytime the app runs, but always in the form of FILE (that's easier for the clients do restore). But you are totally right! The "safe" way would be to make the backups in SQL form (just as we do with MySQL and PostgreSQL). On the other hand, that would go against the simplicity that users expect from the INTEGRATED H2 engine! On Wednesday, January 14, 2015 at 5:06:21 PM UTC, Thomas Mueller wrote: > > 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.
