Question

Was wondering if it is recomended to pass a database connection object around(to other modules) or let the method (in the other module) take care of setting it up. I am leaning toward letting the method set it up as to not have to check the state of the connection before using it, and just having the caller pass any needed data to the calling method that would be needed to setup the connection.

Answer 1

Personally I like to use tightly scoped connections; open them late, use them, and close them (in a ‘using’ block, all within the local method). Connection pooling will deal with re-using the connection in most cases, so there is no real overhead in this approach.

The main advantage in passing connections used to be so that you could pass the transaction around; however, TransactionScope is a simpler way of sharing a transaction between methods.

Since the classes are implementation specific, I’d write each to open it’s own native transaction. Otherwise, you can use the ado.net factory methods to create the appropriate type from the config file (the provider name).