My general approach to new features is to encourage people to
implement them using driver-private methods or DBIx::* modules first.
We can discuss spec changes once we've got some real-world experience.
I think connection pools could be implemented as a DBI sub-class or via
the Callback mechanism.
I have been doing a little research into connection Pooling with OCI and
I was just wondering if the concept of a "Connection Pool" would fit
into the DBI spec someplace.
As we already have DBI::Apache and "connect_cache" would it just be
redundant to add this "connect_pool" as the present f
