Got it, we'll give that a whirl without the delete for backup/restore. The thought on doing the delete database ahead of restore was to be sure to clear out any swapped temp files from large queries, etc. Looks like the EXCLUSIVE mode should clean all that up for us.
Question: For the export/import use case, where the goal is to re-load the data in order to optimize the store (ie.. defrag) after a large number of deletes-- how should that work without doing a delete database? Would we have to drop all the db objects (tables, indexes, sequences, etc) before the import? Thanks, Matt On Monday, July 29, 2019 at 10:01:04 AM UTC-5, Noel Grandin wrote: > > > You can't go EXCLUSIVE and then delete a database. > But perhaps you mean overwrite, in which case this flow should be fine. > > -- 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/a80d477a-4fbd-41ed-8f18-39ae141209ae%40googlegroups.com.
