That is exactly why I use H2. Our systems or made up of independent scripts that implement subsystems and are completely self-containing, meaning they implement their own (Web) user interfaces and contain their own resources and database. Such subsystems can just be copy/pasted to create new ones based on existing ones.
I have developed a two-level JDBC connection cache for this. Connections are accessed by key (driver, url, user, password) and the cache limits the total number of open connections (and optionally the number of open databases/keys and the number of connections per database/key). I do not think using a connection pool per session is a good idea... -- 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 post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/h2-database. For more options, visit https://groups.google.com/d/optout.
