That is nice to know Steve but it is absolutely no good to me. For legal reasons we can not use any third party tool or library that is not marked stable by its providers. There is absolutely no relation with quality in there, its all about what it is called. We are also using some poorer-quality libraries but at least these are formally released.
We are still at 1.3.176 knowing 1.4.x contains a lot of fixes that would benefit us a lot. All we need is some form of formal release version that contains the fixes. I don't mind the version number. Will go for 1.3.177 but 1.3.5.x would be fine to me, as would be 1.4.x. I do not care for backward compatibility with 1.3.176 databases, nor do I care for forward compatibility with future 1.4.x releases, I just need a release build with bug fixes. I can understand the hesitation releasing the MVStore stuff. And that is fine with me. Disable it in some special build to accommodate users like me. Just as long as it is a release version. When I started with H2 there was a very decent two-month average between new releases. A two and a half years stall is really hurting. On Wednesday, December 21, 2016 at 10:05:57 AM UTC+1, Steve McLeod wrote: > > Leon, > > Although not marked stable, 1.4 with the page store (MV_STORE=false in > JDBC URL) works better than 1.3.176 in many ways, and as good as 1.3.176 in > all other ways. > > I'm willing to state this because my product (Poker Copilot) has been > using H2 since 2009 with thousands of users. As of January 2016 we switched > to H2 1.4 (with the page store only) and have had no H2 problems. > > > > >>> -- 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 h2-database+unsubscr...@googlegroups.com. To post to this group, send email to h2-database@googlegroups.com. Visit this group at https://groups.google.com/group/h2-database. For more options, visit https://groups.google.com/d/optout.
