I'd be inclined to have a connection pool per session. Then create and
destroy the connection pool. That way it will manage connections however
you want to use them and you don't have to keep a control connection
open on the database.
But there are so many ways to do it!. It always confuses
Is that metadata all unloaded upon closing that particular database? I
expect to shut down any database not currently in use by a user.
On Thursday, July 2, 2015 at 6:22:34 AM UTC-7, Noel Grandin wrote:
Just note that we load all metadata for a given database into memory at
startup.
Some
Regarding Vaadin, the Application class/idea was one of the major changes
in Vaadin 7 from Vaadin 6. That class/idea are gone. Now we have the much
more flexible VaadinSession that wraps a Servlet session, and owns one or
more instances of one or more UI classes. Each UI instance is the
entire
Just note that we load all metadata for a given database into memory at startup.
Some people opening lots of little databases that spend most of their time inactive have experienced memory problems
because of this.
Other than that, it should work fine.
Let us know if you run into any
Is it possible to start up and shut down multiple H2
http://h2database.com/html/main.html databases within a JVM?
My goal is to support multi-tenancy
https://en.m.wikipedia.org/wiki/Multitenancy by giving each user/account
their own database. Each account has very little data. Data between
Yep no probs at all. You can have multiple databases open at the same
time and open and close them on different threads as you like.
You'll just need to do the appropriate connection handling linked to the
session open / close.
Scaling is going to depend on your application architecture too.
