Hi, What I could do is make H2 version 1.4.192 "non-beta" now. I didn't want to do that because for some use cases (according to Steve McLeod), performance was not great with versions up to and including 1.4.191, and I didn't know about 1.4.192. But now I have confirmation from Steve McLeod that performance improved almost to the PageStore level. Not quite as good, but relatively close. As for stability, I didn't see any major problems with version 1.4.191 and 1.4.192.
What is a bit unexpected is that the jar file of 1.4.192 is compiled with Java 7, which doesn't match the documentation. This is my mistake. Or, probably easier, is to release version 1.4.193 soon, and mark that as stable. Regards, Thomas On Tuesday, June 7, 2016, Dennis Wagelaar <[email protected]> wrote: > It's the same for us: we use H2 in production as well, as a client-side > database that caches part of the server-side database for offline use. If > there's ever an inquiry into the cause of a particularly painful data loss > of offline recorded data, using a beta version of a database engine is > enough to conclude the inquiry. We are currently looking at the following > timeline: > > - 2011: choice of database engine: HSQLDB is inactive since 2010, H2 is > actively developed: we chose H2 > - 2014: last stable release of H2 > - 2015: HSQLDB development restarted; 2.x release series > - 2016: still no stable H2 release > > We're currently using H2 1.3.168: Upgrading to 1.3.176 has resulted in > several cases of database file corruption, so we never pushed that to > production. As a result, we're currently stuck with 1.3.168. > > Op maandag 6 juni 2016 10:26:57 UTC+2 schreef Silvio: >> >> Thank you for the info. I am still very uncomfortable using something >> that is marked as beta in production. But this beta status has lasted for a >> long time already and it is unclear when an actual release version will be >> available. And in the meantime I have seen multiple remarks about things >> that have been improved in 1.4 wrt. the PageStore. >> >> Personally I would have preferred a release status for 1.4 as soon as the >> software was reliable enough to warrant use in production, regardless of a >> possible format change. Why not call that 1.5, 1.6 aso. to mark such >> backward incompatibility? >> >> >> On Sunday, June 5, 2016 at 9:15:19 AM UTC+2, Noel Grandin wrote: >>> >>> We use 1.4 in production with both PageStore and MVStore, both are >>> pretty stable. >>> >>> We currently find PageStore to be slightly more stable when running on >>> some systems in the field where power outages are extremely common (i.e. >>> more than once per day), but even there we are thinking of moving to >>> MVStore with the latest 1.4 builds. >>> >>> The only downside with MVStore is that there might be a binary format >>> change at some point in the future, which will need need a full dump and >>> restore to upgrade across. >>> >>> >> -- > 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] > <javascript:_e(%7B%7D,'cvml','h2-database%[email protected]');> > . > To post to this group, send email to [email protected] > <javascript:_e(%7B%7D,'cvml','[email protected]');>. > Visit this group at https://groups.google.com/group/h2-database. > For more options, visit https://groups.google.com/d/optout. > -- 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.
