On Wednesday, 21 December 2016 20:15:40 UTC+13, Noel Grandin wrote: > > MV_STORE is a completely separate storage engine from the old PageStore. > > The old PageStore engine generates files with a .h2.db extension, the new > MV_STORE engine generates files with a .mv.db extension. > > So it's not possible to mix and match opening the same files with the > different engines. > > I and some other people currently use MV_STORE in production, but there > may still be some issues. If you have .h2.db database files from the 1.3 > series that you want to carry on using, then you will need to use the old > PageStore engine. > > Thanks Noel for such a clear explanation of the situation :-)
As I understand it, eventually all h2 databases will be MV_STORE ones? In which case I'm going to need to migrate my .h2.db file sooner or later? IOW I may as well do it now, esp since 1.3.176 gives me an error and I'd rather move beyond 1.3.167. How do we migrate to the MV_STORE format? -- You received this message because you are subscribed to the Google Groups "H2 Database" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/h2-database. For more options, visit https://groups.google.com/d/optout.
