Hi, Might be silly questions (already asked or answer already written somewhere):
- Will be there other 1.3.X versions or now it is only 1.4.X versions ? - According to website, the way to deacivate MVStore in 1.4, thus failing back to 1.3 way but with the last correction included is done "by appending ";MV_STORE=FALSE" and/or ";MVCC=FALSE" to the database URL". But in the very same sentence, the words "For testing" are written. Does this mean that reverting back to "old" way (not MVStore) is not supported/not recommended in production from 1.4.177 ? Cheers, Frederic Le mardi 6 mai 2014 07:44:01 UTC+2, Thomas Mueller a écrit : > > Hi, > > Is there a documented numbering strategy, somewhere? >> > > Yes, higher numbers are better :-) > > Maybe H2 should not be at version 2.x or 3.x according to "Semver". But > for normal users, there are actually no API changes. The JDBC API is still > the same, and SQL didn't change either. The biggest change is the file > format change, which means you can't easily go back to an old version, but > as far as I see this only requires a minor version change in "Semver". > > In any case, you probably wouldn't reach numbers as high as 176 with this >> numbering scheme. >> > > This is the build number for H2. It is used in error messages as well. > > Regards, > Thomas > -- 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 http://groups.google.com/group/h2-database. For more options, visit https://groups.google.com/d/optout.
