Hold your horses!
I found one more client that accesses the database with version 186.
I had forgotten all about it.
It is a very difficult situation that just one client reading a little
bit from the database will corrupt it.
So beware of version 186 (and maybe others?).
I will regenerate the database this evening make sure all clients are
187 and report if I see any more corruptions.
- Rami
On 8.5.2015 10:36, Rami Ojares wrote:
But my import process as follows:
- Create a new db from scratch
- Create new tables
- import data from the old version using jdbc+sql
- create materilized views (calculated tables), set rights etc.
- turn h2 off in production, copy there the newly created file and
start again.
So I don't think that my current db has ever touched version 186. Is
there a way to see from the db file if it has at some point been
touched by version 186?
- Rami
On 8 May 2015 08:42, "Thomas Mueller" <[email protected]
<mailto:[email protected]>> wrote:
>
> Hi,
>
> I'm afraid if the database was opened with version 1.4.186 (when
using the MVStore), then the data is gone, even if you open it with a
newer version afterwards.
--
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.
