[h2] 1.4.x beta
Hi everybody! While reading your release announces, it makes me both glad and sad at the same time : ) : ( A lot of new great features we'd really love to make use of in our business-critical application, but the 1.4.x branch is still marked as beta. What are the areas that still need stabilization and when do you expect to release the first non-beta, commercial-grade version off the 1.4 branch? Thanks and good luck! Sander. -- 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 http://groups.google.com/group/h2-database. For more options, visit https://groups.google.com/d/optout.
[h2] 1.4.x stability
Hi, we're using H2 1.3.176 to back up a 24/7 Play!-based application, average database size ~100 Mb, persisted to file system. We have some performance problems. I thus have a very general question - when do you think 1.4.x branch would be stable enough to end the beta, and how would you assess the stability right now? Would you recommend to update to the current latest beta, or rather not? Thanks a lot! -- Sander Sõnajalg ZeroTurnaround -- 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 http://groups.google.com/group/h2-database. For more options, visit https://groups.google.com/d/optout.
Re: [h2] Row not found when trying to delete from index [v1.3.174]
Hi, so this is basically a known issue? And as I understand from your context, you are currently lacking a test case that would reproduce the issue? I can't provide one at the moment either, as I can't acquire the customer's database that reproduces this (and it doesn't occur in our own environment). But sooner or later I might also be able to get a database instance that is affected by this.. should I then convert it into a ticket and provide a test case? Anyhow, maybe you have some recommendations about what to try to resolve this..? Dropping and recreating the index probably doesn't provide a final solution, as i read from other threads. Thanks! Sander. I'm afraid MVCC is still experimental in that release. It works for some people, but not for everybody. I know this is no help, but regarding the experimental options, I have seen -- 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 http://groups.google.com/group/h2-database. For more options, visit https://groups.google.com/d/optout.
