Folks, I am looking at embedding H2 into a larger project that I'm working on (see http://blog.lostlake.org/index.php?/archives/94-Lift,-Goat-Rodeo-and-Such.html )
Specifically, I'd like to have H2 instances persisted in some backing store (HFS, Cassandra, ??), materializing the H2 instance out of the backing store, run a series of transactions on the H2 instance and then persist either the new H2 state or alternatively the H2 logs to the backing store. The next time the H2 instance is needed, it will be recalled from backing store, have any transaction logs applied and be ready to go. I've spent about an hour traveling through the H2 source to see if there are obvious places in the code to add hooks for the above functionality, but, well, I got lost and figured I'd ask for pointers to where in H2 such hooks could be inserted. Thanks, David PS -- Any changes/enhancements I make to H2 will be offered back to the community. PPS -- I love H2... it's now the default database for new Lift projects. -- 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.
