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.
