Hi Thomas, On Jun 14, 8:27 pm, Thomas Mueller <[email protected]> wrote: > Hi, > > This is a good idea. I didn't have time yet to look at the details, > but once it's ready it could be included in H2, specially the > Migrate.java (in the package org.h2.tools, in the regular H2 jar > file).
I think Migrate.java should be located next to the 1.2.128 classes. > > The best solution would be if conversion happens automatically when > opening the database using the default driver, but that may be too > complicated to implement. For example by appending ;MIGRATE=TRUE to > the database URL. I don't think an additional parameter is neccessary. What else should H2 do if an old DB is detected? It shouldn't be hard to implement, we only need some sort of plugin registration, so the mig .jar can register to h2. In Driver.java there should be the call to the "plugin". > > The h2mig-1.2.137 file contains both the newest and the refactored > (renamed) 1.2.128, right? Yes > Or are the any changes within 1.2.128? There are some changes needed, eg. START_URL = "jdbc:h2v1_1_to_v1_2:" so that it doesn't clash with the current version. > Is it > important to have one combined jar file? It may be easier to just have > the refactored 1.2.128 as a jar file, so it's not required to create a > new jar file each time there is a regular H2 release. If you can implement a plugin mechanism to allow the current H2 version to call my refactored 1.2.128 jar, this would be very nice. If people need one .jar I could provide h2mig in addition to the separate ones then, too. Regards Christian > > Regards, > Thomas -- 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.
