I'd advise against this approach as it leave your open connection idle most
of the time it's left open. Open the connection, use it, then close it. This
releases the connection as soon as possible, and since connections are pooled
then someone else in the application can use the same connection once you're
done with it. This will result in less wasted resources.
-Brock
DevelopMentor
http://staff.develop.com/ballen I am writing a web app that is very Database intensive.. I have to
open and close db connections all over the place. I was wondering if
there is any reason not to open the db connection in the session_start
event, so the connection is availbale for the entire seesion?
