This is Issue 1179 moved from a Google Code project.
Added by 2012-11-22T17:21:31.000Z by michael....@gmail.com.
Please review that bug for more context and additional comments, but update this bug.
Original labels: Type-Enhancement, Priority-Low
The actual connection Pool in Orientdb lacks of some needed functionality in bigger environments:
Timeout for dbs not used
Timeout (true / false)
Listeners / Hooks - you can operate with if a connection is established
(for example -> is the database available or should it be created)
Listeners - on Close of database - make operations necessary (cleanup - Format C: or whatever you need)
Listeners - on Open of Database
Hope this is enough input -> Luca we send you our implementation - maybe you could reuse something ....
Often you have a DB-layer (with connection pool) between your application and the underlying database - initialized with some passed connection properties (DB-Name/User/Password).
To be able to write unittests against an in-memory database it would be nice to have a connection pool that supports something like OObjectDatabasePool.global().acquire("memory:...").
Are you sure that this issue is valid ?
Well because no one minds, I will close the issue.