Hi We have this use case that we're replacing an Oracle database with an embedded H2 in our JUnit integration tests of a particular component. In the setup phase of each test we launch an embedded H2, create tables and inserts data. Now when we have more than a thousand tests this is starting to take time.
Is there a way of today to take an in memory snapshot of the embedded database once we have created the tables and inserted initial data so that it is a fast operation to reset the database to that state for each test case? (I guess having this involve disk I/O is too slow) If not, would it be feasible to implement as a feature or is there some inherent problem with serializing the state of H2 in memory and resetting it again to that previous state? BR Johan -- 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 https://groups.google.com/group/h2-database. For more options, visit https://groups.google.com/d/optout.
