How I'm thinking. The connections are normally in pool, when you're
using some, it's not in pool (actually it's still in the pool's
collection, but "marked as used") logically. When you're cleaning all
pools you are cleaning connections that are pooled (in pool). Hence
connections not in pool should be untouched. At least that's what I
think. On the other hand, this a huge breaking change. Not sure it's
worth changing it. :\
Also thinking from the other hand. If you have reference to some
connection that's used and you'd like to close and clear all, why not
to first close connections you're holding and then clean pools. Right?
What's to reason to have method that would do it under your hands...
--
Jiri {x2} Cincura (x2develop.com founder)
http://blog.cincura.net/ | http://www.ID3renamer.com
------------------------------------------------------------------------------
Try New Relic Now & We'll Send You this Cool Shirt
New Relic is the only SaaS-based application performance monitoring service
that delivers powerful full stack analytics. Optimize and monitor your
browser, app, & servers with just a few lines of code. Try New Relic
and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_apr
_______________________________________________
Firebird-net-provider mailing list
Firebird-net-provider@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/firebird-net-provider
