We keep running into this scenario where it seems that there are a set of URL parameters for the 'management' or 'server-side' connection that we want and a different set for the client-side.
When using tcp:// for client-side, it is straight-forward. However, when trying to use file: for client-side (for performance reasons), it does not seem possible right now. Is there a strategy for allowing client-side file: connections to not connect if there is not already one connection (aka the management or server-side) running? We were looking at hack-ish alternatives like creating and deleting symlinks so the IFEXISTS check would fail. That creates a hacky race condition and isn't deterministic as it should be. Has anyone solved this another way or would this be a feature enhancement? Thanks! -Matt -- 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/64fe12f3-67a0-40fa-9327-20bba020a1cb%40googlegroups.com.
