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
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
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
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
I still get the following message using the latest version of the H2 jar
via maven:
[23505][23505] Unique index or primary key violation: "PRIMARY KEY ON
.PAGE_INDEX"; SQL statement:
I have a join table that seems to be the culprit - it uses a composite
primary key with foreign key
