Hi
On 11/9/2024 4:47 AM, Andrei Tokar wrote:
Forgive me for a possibly stupid question, but why this feature is so badly
needed?
What's wrong with populating database to a desired state, shutting down,
copying the file, and starting H2 with a file copy.
Why do you need this functionality for in-memory (non-persistent) database? If performance is the reason, you can use
RAM-based file system instead.
Just noting that in the time I have been working on H2, this is the third time
this feature has come up.
Some people want to (a) have their test database at a known point (b) run a _lot_ of unit tests and (c) have their unit
tests run relatively quickly.
So for all it's shortcomings, I think it would be a useful addition (Plus I am tickled pink that such afeature could be
implemented in so few lines of code, thanks to H2's excellent internal architecture)
Regards, Noel Grandin
--
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 view this discussion visit
https://groups.google.com/d/msgid/h2-database/5fad353b-be76-45d9-bb39-1817db1c4c0a%40gmail.com.
