Re: [h2] Unique index or primary key violation in version 1.4.191
I have not tested the scenario with MVCC off because that is pretty much a non-starter for our performance requirements. It is kind of an odd bug because the application, the embedded h2 web console, and the h2 shell do not have a problem with the database file. Only other database viewers seem to have the problem - of which I certainly do not have an exhaustive list. When I started looking into the bug I did not realize that I'd be able to access the database file via the H2 shell, so it was initially a higher priority bug. As I mentioned, the most important thing for me that has come out of this is learning about MVCC support/stability for PageStore. Noel mentioned it is not a priority for them, which I totally agree with, and I would not want anyone to spend more of their time trying to research this because the solution for me is to switch to MVStore and to use the H2 shell instead of some of db viewer. On Wednesday, February 17, 2016 at 7:08:20 AM UTC-6, Kartweel wrote: > > I've been using MVCC with PageStore for years. LOBS don't work very well > (but I didn't want them in the db anyway, so we don't use LOBS). Haven't > had any issues with anything else though. > > Doesn't mean bugs don't exist though. > > You only get the issue with MVCC on though hey? > > On 17/02/2016 1:18 PM, Noel Grandin wrote: > > At some point in the future is all I can say, not anytime soon. My > > point was more that MVCC on PageStore is a dead end for us, so we're > > not going to expend any effort debugging problems with it. > > > > So if you want reliability, use PageStore without MVCC. > > > > > -- 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.
Re: [h2] Unique index or primary key violation in version 1.4.191
I've been using MVCC with PageStore for years. LOBS don't work very well (but I didn't want them in the db anyway, so we don't use LOBS). Haven't had any issues with anything else though. Doesn't mean bugs don't exist though. You only get the issue with MVCC on though hey? On 17/02/2016 1:18 PM, Noel Grandin wrote: At some point in the future is all I can say, not anytime soon. My point was more that MVCC on PageStore is a dead end for us, so we're not going to expend any effort debugging problems with it. So if you want reliability, use PageStore without MVCC. -- 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.
Re: [h2] Unique index or primary key violation in version 1.4.191
At some point in the future is all I can say, not anytime soon. My point was more that MVCC on PageStore is a dead end for us, so we're not going to expend any effort debugging problems with it. So if you want reliability, use PageStore without MVCC. -- 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.
Re: [h2] Unique index or primary key violation in version 1.4.191
Do you know of any timelines to disable MVCC support in PageStore? I don't see it listed in the roadmap http://www.h2database.com/html/roadmap.html but I do see that the removal of at least one PageStore feature is being called out. -- 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.
Re: [h2] Unique index or primary key violation in version 1.4.191
I spent some time trying to recreate the issue with a simple table set up but was not able to. There must be something else in my database schema that is contributing to the problem. Interestingly enough, when I use the org.h2.tools.Shell to view my h2 database, I am able to connect to it successfully and am able to browse the database with no errors. As a result of this topic I at least know that 1) I can use the h2 shell or embedded h2 server to browse a database with this error, and 2) I need to migrate away from PageStore and MVCC to MVStore. Based on what you said about the support and future PageStore and MVCC, and the fact that I have a workaround, I don't think it makes sense (for me and my company) to pursue researching this bug further because we will be migrating away from PageStore. Thank you very much for your clarification and help on the issue. On Tuesday, February 16, 2016 at 12:30:45 AM UTC-6, Noel Grandin wrote: > > Of course,it could also be that you've uncovered another tricky corner > case - in which case we need some kind of > standalone test case to be able to debug it > -- 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.
Re: [h2] Unique index or primary key violation in version 1.4.191
I'm working on creating a standalone test and will update once I have one. Thanks! On Tuesday, February 16, 2016 at 12:30:45 AM UTC-6, Noel Grandin wrote: > > Of course,it could also be that you've uncovered another tricky corner > case - in which case we need some kind of > standalone test case to be able to debug it > -- 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.
Re: [h2] Unique index or primary key violation in version 1.4.191
Of course,it could also be that you've uncovered another tricky corner case - in which case we need some kind of standalone test case to be able to debug it -- 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.
Re: [h2] Unique index or primary key violation in version 1.4.191
Unfortunately, the MVCC stuff for the PageStore engine always had a couple of corner-case bugs that we never managaed to squash. At some point we will remove that setting since the new storage engine (MVStore) is inherently MVCC -- 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.
