Re: [phplib] performance From: nathan r. hruby (nhruby <email protected>)
Date: 11/30/00

On Thu, 30 Nov 2000, Chris Cochella wrote:

> This thread is helpful.
>
> A couple more questions:
>
> > phplib-7.2a also used to leave tons of open connections laying around, if
> > you have't, change up to 7.2c it should help the out of connection
> > problems. Also, make sure you're destroying
>
> How do you destroy them? I thought phplib destroyed then after page was
> finished. Correct/incorrect?
>

php end ends processing and destroys objects at the end of run, but
manually destrying objects can help convince the parse engine to release
connections back into the pool, and hopefully close the connections
instead of leaving a hanging one with an open table in MySQL

The downside is that there is no destroy() metoh in db_mysql.inc, so
you'll need to destroy the object your self. If you paw around in there I
think there is some connection close / link release stuff myou can always
just be brutish and unset($my_phplib_db_object);

>
> > and / or reusing db objects as
> > opposed to just starting a new one every time you need db access.
> > (destroying the object will release the connection back to php's
> > conenction pool)
>
> What is it about 7.2c (which file(s))? What are the changes?
>
> I am running 7.2b and not likely to upgrade soon as there seem to be
> significant changes in the database tables. I would like to modify
> 7.2b to take advantage of this.

You're thinking 7.3-dev 7.2c is a drop in replacement, no muss, no fuss.

-n 

-- 
........
nathan hruby
Webmaster: UGA Department of Drama and Theatre
Project Maintainer: phpSlash, Carousel
nhruby <email protected>
........

---------------------------------------------------------------------
To unsubscribe, e-mail: phplib-unsubscribe <email protected>
For additional commands, e-mail: phplib-help <email protected>