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. -- William Kimball, Jr. "Programming is an art-form that fights back!" "John Nichel" <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED] : William wrote: : : > If you read the code I posted, you'd see that I am sending valid resources. :) As I explained, I lifted the technique : > directly from the PHP documentation. Now, if you can see a bug in my implementation of this technique, by all means, : > please point it out. : > : : "Please limit replies to constructive workarounds." : : Well, since you *know* that all your resources are valid, why don't you : echo out mysql_error() after you make a mysql function call. : Constructive enough for you? : : -- : 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
