Hi,
We have been using H2 for a while now and have occasionally received the
following exception when records are read just after being written (often
by a different thread):
Caused by: org.h2.jdbc.JdbcSQLException: IO Exception:
java.io.IOException: org.h2.message.DbException: IO
Hi
There is some kind of constraint corruption here - the foreign key has become associated with the wrong index
internally. Not sure how that happened. It was probably a bug in an earlier version that we've fixed already, since I
could not find a sequence of commands that managed to replicate
You appear to be running version 1.3.172.
We have fixed quite a few LOB related issues in the last couple of versions, so it's probably worth your while updating
to 1.3.174 and seeing how that goes.
On 2013-11-12 11:02, Daniel Stone wrote:
We have been using H2 for a while now and have
Hi,
I'm afraid the current implementation does not support it. Of course this
could be changed, actually I guess it would be relatively easy to remove
the check.
At some point I think it's better to re-implement clustering. But first my
priority is to work on the new storage engine (the
Thomas,
This sounds like a good plan, and I realize there is a strong priority for
the MVStore.
When I look at the other major DBs: MySQL, Mongo, etc. They all seem to
have a feature to allow replication for faster reads. While H2 may fit a
different market than these other DBs, but it
thx
--
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.
