Hi. I took a look at the standalone migration and the modified H2 database Christian made. i noticed both contains the entire H2 source for the old version. Most applications who wish to migrate already have a H2 database jar file included and now they have to include another H2 with everything in it of an older version to do the migration. Why not rather then having a 'second H2 database' to be added to classpath for migration, we might as well have a lightweight format converter that utilizes the H2 that the application have and do a 'one-to-one' direct file format conversion ? In this way, you don't need to add more bulk and have something lightweight.
Here's some numbers for my application: H2 jar v1.2.137: 1.1 MB H2 standalone migration tool: 1.3 ~ 1.4 MB Total: ~2.5 MB It isn't really big in modern standards but the H2 jar have nearly the same files as the migration tool. If that's the case, why not directly feed on the H2 jar ? I was wondering if the H2 migration process is using the old version in the mig. tool to export out the data in sql then reload the exported sql to the new version. If that's the case... why not a 'one- to-one' file convert ? It would be probably even more lightweight then to export sqls and all those (since database parsers... engines are required). Regards, Thotheolh. On Jul 4, 4:25 am, Christian Peter <[email protected]> wrote: > Hi, > > the old really standalone tools are linked in the first message of > this thread. They are obsolete now. > > The new official migration .jar addon is > herehttp://h2database.com/h2mig_pagestore_addon.jar > and can be used with the next release (it is now included in SVN). > > Regards > > Christian > > On Jul 3, 11:04 am,Thotheolh<[email protected]> wrote: > > > > > Hi Christain. May I know the url to the standalone migration jar file? > > I tried to search the h2 website for the standalone download but > > couldn't find it. > > > Thanks alot. > > > Regards, > >Thotheolh. > > > On Jul 3, 4:54 pm, Christian Peter <[email protected]> > > wrote: > > > > HiThotheolh, > > > > Thomas and I work on a solution which soon will be integrated and will > > > eventually has the following features: > > > > - Default H2 release can be used > > > - Standalonge migration .jar is available from the h2 homepage > > > - If H2 finds the migration classes, it will convert the database via > > > "script to" and "runscript from" automatically > > > > This should meet your requirements. > > > > Regards > > > > Christian > > > > On Jul 3, 7:35 am,Thotheolh<[email protected]> wrote: > > > > > 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.
