I can accept that as a workaround, but I was hoping to do more than merely mute the warnings. Is there a way to truly use the connection and result set handles? Can PHP truly utilize it's own connection resource handles in code?
Bottom Line: This is going to make a real mess when multiple database connections need to be used and when multiple query results need to be managed simultaneously. -- -- William Kimball, Jr. "Programming is an art-form that fights back!" "John Nichel" <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED] : William wrote: : : > Since posting the original copy of this message -- which, in 10 hours, never appeared on this newsgroup -- I upgraded : > from PHP version 4.3.4 to 5.0.1. Unfortunately, the same exact problem persists. I'm starting to believe this is a bug : > in PHP's MySQL memory management functions. : > : > Original Post: : > ------------- : > I've set up several tests to try to find some way to get the mysql_close() function to work without throwing warning: : > : > Warning: mysql_close(): ## is not a valid MySQL-Link resource : > (where ## is some number like 18 or 39) : <snip> : : @mysql_close(); : : -- : By-Tor.com : It's all about the Rush : http://www.by-tor.com -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
