On 21/07/2013 1:03 AM, Thomas Mueller wrote:
But still, there is a risk. This was one reason for me to start
working on the new storage engine MVStore: to reduce the risk of
corruption (the MVStore is quite a bit simpler than the current,
traditional storage engine). It is still work in
Thank you Bill for the feedback. I've been lucky so far that I haven't run
into any issues but our tables are much smaller than yours. It's good to be
aware of that risk when we grow our data.
When the problem (losing index) happens, did you experience corrupted
tables, or just a performance hit
Hi,
The most stable version is usually the second-latest version. Reason: Bugs
are fixed as they are found so the latest version in theory should have the
least bugs; but the latest version is new so it is less tested.
I did a search in the mailing list for database corruption.
Yes,
Hello all,
I am Bill Torcaso and I have been lurking here for a few months. And right
up front, I want to say that H2 is well-supported and good for small to
medium data set sizes.
We use H2 to hold very large amounts of data - 20GB up to 80GB. And I have
seen a problem, multiple times, but
