We are working through maintenance scenarios, and have hit a roadblock on blocking client connections and re-starting a shutdown database. This is problematic when clients use pools and auto-reconnect.
Scenarios: 1. Blocking new clients from connecting during backup / restore or export / import 2. Re-starting a database after performing a shutdown to compact Questions: 1. Is there a command to start the database after a shutdown? Or a mechanism where the database.open() could be called again through a user-defined function? 2. Is there a combination of client-side connection flag(s) that would prevent the engine from starting the database if its not already running? Similar to IFEXISTS=TRUE, but more like IFRUNNING=TRUE Thanks! -- 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/292678cb-8d84-4258-a22c-46eb923e55fa%40googlegroups.com.
