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 [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/h2-database. For more options, visit https://groups.google.com/d/optout.
