Hi,

> The reason for using the same connection for "switching" the DBs is
> to avoid too many Connections to the server. DBs like MySQL, Oracle
> have provisions to switch the DBs like this (and also carry-over
> transactions) at runtime. For example the MySQL has the catalog
> support and the Oracle has a "Alter session.." support. This way, we
> will be able to avoid many I/O connections and at the same time work
> with multiple DBs in the same database server. To sum it up, its
> purely for optimization purposes. It'll be good if Firebird too
> offers such a support, otherwise, we need to go for connection/DB
> approach only.In our application we will have many database in
> single db sever. Depending upon request we will switch database,

Please post this as a fature request in the Firebird-Support or
Firebird-Architect list.

From my personal experience time needed to establish connection can be
neglected compared to the time needed to compile and execute statements.
AS3AP test suite shows only slight peformance improvement when using
connection pooling compared to the improvement when statement caching is
used. In case of Firebird you can rely on opening new connection to a
database when needed, but transactions will remain database-local unless you
use XADataSource and a distributed transaction coordinator.

Roman