Hi, > if there's nothing in the change > log indicating that I really should?
Not necessarily, that's true. The only issue that affects stability may be in version 1.1.114: In some situations, an ArrayIndexOutOfBoundsException was thrown when adding rows. This was caused by a bug in the b-tree code. > (effectively taking regression risks) Upgrading is always a risk. The risk can be reduced with test cases. There are quite many test cases for H2. If you want to reduce the risk, I suggest to implement and run tests (for example randomized tests). >> The reason could be that the index was re-built when opening due to a >> bug that was fixed in version 1.1.112: "...indexes were always >> re-built unnecessarily when opening" > > Here again I was using 1.1.111, so I'd assume not. > Could this database dump be, however, of any use to you? I'm not sure if it will help in this case. It only helps if the problem can be reproduced. In any case, I suggest backup a database from time to time to SQL script using SCRIPT TO '...'. Regards, Thomas -- 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=.
