Re: How can a script tell if there's a MySQL problem?

Per Jessen wrote: > Nathan Rixham wrote: > >> Bastien Koert wrote: >>> 1. Make sure you are freeing up all resources as soon as you can -> >>> mysql_close(); >>> >> >> little thing I've done for some time that's stuck with; (php5+ only) >> >> on all of my database connection classes, I have the db close >> function in the destructor just to make sure > > I guess it depends on the type of application - for a web-transaction > running on a web-server, why bother? It'll clean up after itself > anyway. Actually, for reusable code intended for others to use, it might just be a safe precaution. /Per Jessen, Zürich