On Wed, 17 Apr 2013 10:29:57 +0200, Jiri Cincura <disk...@cincura.net> wrote: > Hi *, > > I just found behavior that surprised me. Suppose pooling is on and > (all connections to same database): > Open connection1. > Open connection2. > Close connection2. > FbConnection.ClearAllPools(); > Try to use connection1. > > On this ^ line you'll get exception as the connection1 was also > cleared aka closed/disposed. I always used ClearAllPools with all > connections closed so I had no idea it behaves like that. > > But do you think is correct? Should the ClearAllPools clear even the > opened connections?
This behavior matches with my expectations for a method called ClearAllPools(). Maybe you should keep the existing behavior and add a method 'ClearAllPools(bool closeOpenConnections)' which allows explicit control over this behavior. Mark ------------------------------------------------------------------------------ Precog is a next-generation analytics platform capable of advanced analytics on semi-structured data. The platform includes APIs for building apps and a phenomenal toolset for data science. Developers can use our toolset for easy data analysis & visualization. Get a free account! http://www2.precog.com/precogplatform/slashdotnewsletter _______________________________________________ Firebird-net-provider mailing list Firebird-net-provider@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/firebird-net-provider
