I felt that what we need is just a standalone official "migrate.jar" or a compact package of tools downloadable on the H2 website. As long as the H2 file storage format doesn't change, then the migrate tool would not be updated and allow cross migration between different formats of H2 storage if ever there's any more H2 file formats to be created.
In this way, we would have a highly compact migration tool not stuck to any H2 version where you need certain old versions of H2 (1.2.128) to open the database and migrate then you jump back to the latest (1.2.138). That's not going to be an elegant solution. With a standalone migrate tool, the user could simply just add it to the application and run file format migrations quietly so as not to alarm the app user and the main H2 distribution could remain as light as possible not weighted down by an additional migrate tool. I have a couple of applications I made still running the old format and I could not migrate them without running into complex troubles and using modified distributions. Sorry, Christian, your modified distribution is a good idea but the problem is that for every new H2 release, you need to release a modified distribution and this is not elegant solution to the long standing issue. For now, if I want to migrate my old H2 format to the page store, I need Christian's modified package but I hope an official standalone migrate tool would forever solve this unresolved issue. Looking forward to the final elegant solution to put this unresolved issue to rest. Regards, Thotheolh. -- You received this message because you are subscribed to the Google Groups "H2 Database" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/h2-database?hl=en.
