Whoops! Forgive me, I meant to say a CGI environment. This should be a lesson to me to proofread no matter the time restraints. :)
----- Original Message ----- From: "Dave Mittner" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Tuesday, February 05, 2002 10:37 AM Subject: Using SQL in a C Program > Most of my experience with SQL comes from an SQL environment in which the > program will run through and end fairly quickly. I'm now up against a > constantly running C program which utilizes the database on a regular basis. > In this case, is it better practice to only open the connection for the > duration of use, or have it open constantly and run a check to reconnect if > it dies for some reason? I'm not sure if there's any correct answer to this, > but I'd welcome opinions. The speed of the connection is of the utmost > importance and if time can be saved by keeping the connection constant, I > think I'd prefer that way. > > Thanks, > Dave Mittner > > > --------------------------------------------------------------------- > Before posting, please check: > http://www.mysql.com/manual.php (the manual) > http://lists.mysql.com/ (the list archive) > > To request this thread, e-mail <[EMAIL PROTECTED]> > To unsubscribe, e-mail <[EMAIL PROTECTED]> > Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php > > --------------------------------------------------------------------- Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail <[EMAIL PROTECTED]> To unsubscribe, e-mail <[EMAIL PROTECTED]> Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
