Hi! I've jest run into a problem with the connection pool. When I reach the limit an exception is thrown.
It seems to me as an suboptimal thing to di in such a case. Con pool is there to gain speed and random exceptions are IMHO too high a price to pay. I think in such a case new connections should be opened and added to the pool. connectionString.MaxPoolSize should decide whether the connection is returned to the pool or closed. I would rather also test connectionString.MaxPoolSize with the "_available" stack and not the "_busy" list. This would make connectionString.MaxPoolSize mean "how many connections you would like to have at hand when you're working with the database" rather than "how many concurrent connections would you like to allow", which I think is closer to the goal of the pool. Such behaviour would be much more predictable to the user. Cheers! Michał Ziemski
------------------------------------------------------------------------------
_______________________________________________ Firebird-net-provider mailing list Firebird-net-provider@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/firebird-net-provider
