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).
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. The h2mig-1.2.137 file contains both the newest and the refactored (renamed) 1.2.128, right? Or are the any changes within 1.2.128? 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. 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 h2-datab...@googlegroups.com. To unsubscribe from this group, send email to h2-database+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/h2-database?hl=en.
