@Noel Grandin- Yeah, that higher-level component is what we are writing. Maybe we don't need to call shutdown to flush all the buffers?
Q: Will this flow maintain data and transactional consistency? 1. Management-Connection: Create database (and start) 2. Client-Connections: do SQL stuff 3. Management-Connection: Call EXCLUSIVE mode enable 4. Clients-Connections: disconnected.. entry retry state 5. Management-Connection: Call backup (or export) 6. Management-Connection: Call delete database 7. Management-Connection: Call restore database (or import) 8. Management-Connection: Call EXCLUSIVE mode disable 9. Client-Connections: re-connect.. resume doing SQL stuff Thanks, -Matt On Monday, July 29, 2019 at 9:23:46 AM UTC-5, Noel Grandin wrote: > > > Startup/shutdown we largely assume is the responsibility of some higher > level component. > > For backup/restore, what we have is SET EXCLUSIVE > http://h2database.com/html/commands.html#set_exclusive > > We have basic infrastructure such code could be built-on, the admin > database stuff, which was, I believe, initially > mostly designed around the needs of the cluster functionality, but you'd > have to write some code yourself to make that work. > > -- 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 on the web visit https://groups.google.com/d/msgid/h2-database/f96d1ac0-28a3-4f22-b8b3-bae9b7f3a043%40googlegroups.com.
