From: bennykuok <be...@ch...> - 2004-12-30 07:12:25
|
Hi, Since the firebird.net data provider does not support the parallel transaction and the multiple transaction per connection, so my question is would the connection pooling would be the alternative way to solve this limitation? If yes, then now bring me another question, that is, do we have to manually create the new connection that within the same pooling or connection with same connection string ? Is there any mechanism on firebird.net provider would detect that the connection is too busy e.g. having the parrallel transaction then would 'automatically' spown new connection within the same pooling ? If it does, how to do so? Or if we have to handle manually, how we should check the state of the connection that require pooling ? e.g. how to do sth like If connection having parallel transaction then spown another new connection ? TIA regards, benny ;-) |