We have a situation where we perform some major pruning of a database (dropping tables, removing columns, deleting a large percentage of the rows) before closing the database a burning it onto a CD.
Very infrequently we run into a situation where when we try to open the database from the CD it throws an exception and won't open because it thinks that it needs to recreate some indexes and/or reconcile the log. I am not at all confident that we are shutting the database down cleanly. There is every possibility that H2 is just doing a good enough job of dealing with incomplete shutdowns that we are just not noticing anything most of the time. We are using H2 in embedded mode, and we basically close the last connection and exiting the process. Is there any way to wait and check with the database to make sure that it is completely closed? I can send more information if it is needed. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
