We are using 1.2.128 and we are encounting the bug that has been fixed in 1.2.131:
"In versions 1.2.129 and 1.2.130, a database could not be opened sometimes after dropping tables or indexes, and then creating new indexes for existing tables. The exception contained the text "parent not found" (version 1.2.129) or "Table not found" (version 1.2.130)." Could you please explain how the error emerges and whether there is a way to work around this? E.g. will the error still occur if the dropping of tables and creation of new indexes happens in two separate transactions, or does it help to close the database in between? (PS: Alas we cannot simply update to a newer version; we're forced to stick with 1.2.128 because we have customers with older installations including h2-1.1.118 and we need the updateability of 1.2.128.) Thanks, Dirk. -- 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.
