The problem turned out to be a run-time bug with object instances (of the same class) stepping on each other. More specifically, PHP doesn't seem to differentiate between a flat script-level $ovConn object and a new instance of $ovConn that gets fired up in an unrelated object's method at run-time. When the latter object unloads, both instances of $ovConn lose their database connection resource handles. I have determined this through extensive debug logging through tracing all method calls. I will troubleshoot this further and try to find a way to get PHP to separate the two instances of $ovConn so one doesn't kill the other's resource handle.
Please keep your responses professional; this newsgroup/list is the first contact for people needing help with PHP -- even if it's their own fault. Your enflamed, emotionally charged reactions help no one and seem only to serve your own ego. This matter is closed. Good day. -- -- William Kimball, Jr. "Programming is an art-form that fights back!" "John Nichel" <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED] : 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. : > : : Go 'challenge' someone else. I gave you a 'constructive workaround', : you didn't like it. I gave you the non-'lazy approach' to help you find : your problem, but you want to take the 'lazy approach' and 'challenge' : us to find it for you. : : It's really simple. If the php mysql functions tell you it's not a : valid link, then it isn't; no matter what you think it is or isn't. Use : mysql_error, break down sections of your code, ensure that you're : getting back/passing data that you think you are, and track the problem : down. That's how to become a better programmer. : : -- : 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
