William wrote:
Why waste time by turning this into an attack? (A rhetorical question, please don't bother addressing it.)
I'm pressing for a better answer now because the workaround you posted simply ignores the problem and because you implied that you got these functions to work -- presumably without having to mute warnings (otherwise, your solution is faulted). Just take a few minutes of your valuable time to read the code I posted. I challenge you to find fault with my management of the resource handles. In the end, we may both be better programmers.
Programming languages do not make things up. If you say mysql_close($anyvariable) and PHP says that $anyvariable is not a MySQL connection resource, then it's not.
No, it's not. Shh. It's not.
If you can reduce what you're seeing to the smallest amount of code possible and still reproduce this problem, then maybe it's a bug. I have 5.0.0 installed and will install 5.0.1 just for you if you can give me the smallest amount of code that reproduces this problem to help you test. Otherwise, use @ and turn a blind eye... ;)
--
---John Holmes...
Amazon Wishlist: www.amazon.com/o/registry/3BEXC84AB3A5E/
php|architect: The Magazine for PHP Professionals – www.phparch.com
-- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
