> > I am by no means an expert, by I always close the connections
explicitly.
> > My understanding is that the connection gets closed eventually, but by
MySQL
> > itself after a time out period.
>
> OK, that makes sense. I didn't want to do that just yet, because
> things have been running fairly
On Sun, Apr 20, 2008 at 12:49 PM, David Krings <[EMAIL PROTECTED]> wrote:
> I am by no means an expert, by I always close the connections explicitly.
> My understanding is that the connection gets closed eventually, but by MySQL
> itself after a time out period.
OK, that makes sense. I didn't wa
Randal Rust wrote:
On Mon, Apr 14, 2008 at 11:13 AM, Daniel Convissor
<[EMAIL PROTECTED]> wrote:
close() is called during PHP's cleanup process that happens at the
end of script execution.
OK, so if I don't have to *explicitly* tell the process to close, then
why do I keep getting a lot of
On Mon, Apr 14, 2008 at 11:13 AM, Daniel Convissor
<[EMAIL PROTECTED]> wrote:
> close() is called during PHP's cleanup process that happens at the
> end of script execution.
OK, so if I don't have to *explicitly* tell the process to close, then
why do I keep getting a lot of threads that are Sl
Hi Randal:
On Fri, Apr 11, 2008 at 06:51:34AM -0400, Randal Rust wrote:
> My understanding is that PHP automatically cleans up a database
> connection after it has executed the query. Therefore, I don't need to
> use the close() function. Is that correct?
No. close() is called during PHP's clean
Randal Rust wrote:
We have been having some performance issues on one of our larger
sites, and I'm trying to figure out the best way to go about fixing
them.
.
On a related note, our main issue is that the site keeps slowing down
and we are getting a 'Too Many Connections' error from MySQ
