
October 3rd, 2006, 11:11 AM
|
|
Registered User
|
|
Join Date: Feb 2004
Posts: 4
Time spent in forums: 40 m 14 sec
Reputation Power: 0
|
|
|
Embedded .Net 2.0 connections
When using the .Net 2.0 client is it better to close the connection after each SQL command/process or cache the open connection? The reason I ask is because I know ADO.Net 2.0 has connection pooling and I wasn't sure if Firbird did something like this internally.
I also noticed that not calling Dispose() on the command object caused my application to eventually run out of memory. Is there a guide for faq relating to best way to use these libraries?
|