Interesting, thanks for the suggestion! Looking through the code now I see that MVStore uses FileStore which uses FilePath which maintains a publicly accessible registry of FilePath implementations, where I could register, for example, a CustomFilePathMem. Cool!
Looking into the fs package, I see that ByteBuffer is used to pass data to and from FileBase, and that, in the case of FilePathMem, data in ByteBuffers makes ultimately makes its way into a byte array in FileMemData. I imagine, for my purposes, that I should be able to simply copy all of the underlying byte data stored in FileMemData after running my liquibase migrations and then, between each test, close/open H2 and restore the backed up byte data into CustomFileMemPath. Thanks, Noel! -- 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.
