Many thanks Darin. I added it to my cfc and the spikes in memory seem to be
under control now.
-Dusty
_
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Darin Kohles
Sent: 01/23/2008 11:51 PM
To: discussion@acfug.org
Subject: Re: [ACFUG Discuss] closing database
Actually, you should wrap your code in a try/catch/finally block. The
closing of the connection should always happen in the finally block to
ensure that it closes if an exeption occurs.
That being said, once this object is out of scope, garbage collection
should close the connection for
That was an excellent thought. I've never used cffinally but just looked up
what it does.
thx
-Dusty
_
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Dean H. Saxe
Sent: 01/24/2008 6:56 AM
To: discussion@acfug.org
Subject: Re: [ACFUG Discuss] closing database
] On Behalf Of Dean H.
Saxe
Sent: 01/24/2008 6:56 AM
To: discussion@acfug.org
Subject: Re: [ACFUG Discuss] closing database connections
Actually, you should wrap your code in a try/catch/finally block.
The closing of the connection should always happen in the finally
block to ensure
--
*From:* [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] [EMAIL PROTECTED]] *On
Behalf Of *Dean H. Saxe
*Sent:* 01/24/2008 6:56 AM
*To:* discussion@acfug.org
*Subject:* Re: [ACFUG Discuss] closing database connections
Actually, you should wrap your code in a try/catch
:45 AM, Dusty Hale wrote:
That was an excellent thought. I've never used cffinally but just
looked up what it does.
thx
-Dusty
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Dean H.
Saxe
Sent: 01/24/2008 6:56 AM
To: discussion@acfug.org
Subject: Re: [ACFUG Discuss] closing
group by email having (count(email) 1)
John
[EMAIL PROTECTED]
_
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Douglas Knudsen
Sent: Thursday, January 24, 2008 9:53 AM
To: discussion@acfug.org
Subject: Re: [ACFUG Discuss] closing database connections
to answer
I've run into a problem with my VPS server at hostmysite. It seems my server
gets really low on memory due to database connections that are left open (so
I'm told by HMS) and HMS recommended this:
--
From HMS support:
SQL memory problems like this usually
