Sorry, I don't think it's an H2 bug now.

Perhaps it's caused by previous abnormal shutdown of H2.
(I think the db file is corrupted by a kill -9 operation)
I'v tried the case in a new test environment, everything is OK now.

-- 
You received this message because you are subscribed to the Google Groups "H2 
Database" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/h2-database?hl=en.

Reply via email to