Hi, Please send emails to the group and not to me directly.
If the database can't be read from the new version, it is required to load two versions of H2 (but not strictly at the same time). H2 automatically does this if the data file is called <dbName>.data.db and not <dbName>.h2.db, but in this case the upgrade jar file needs to be in the class path. If the database is readable from the new version, you should be able to just use the new version of H2 to do the migration. Regards, Thomas On Thu, Oct 18, 2012 at 10:02 AM, sascha frick (empros gmbh) ... wrote: > Hi Thomas > > No problem at all. Your answer is very much appreciated. > Hope you had a good vacation time! > > One last question regarding the migration of existing DBs: The docu > suggests to dump the DB with the old version and then to import the script > using the new version. > Is this the only way or is it save to use the new version to dump the DB? > We ship H2 as part of our software and need to migrate databases upon > opening them. Therefore we would need to load two different version of the > H2 lib at the same time. > > Many thanks! > Regards, > -sascha -- 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.
