FYI: I updated the migration .jar file. Now it's created from the version-1.1.x branch.
Regards Christian On Jul 11, 10:29 am, Christian Peter <christian.peter...@googlemail.com> wrote: > Hi, > > On Jul 10, 8:01 am, Thotheolh <twzger...@gmail.com> wrote: > > > 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. > > The latest version does not contain the source, though, but you are > basically right: It's a full "old" H2. > > > > > 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). > > Because we don't have the time to do that. This is a very complex > task. You are free to develop your one-to-one converter of course. > > Regards > > Christian -- 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.
