Re: can't figure out this mysql error

On Saturday 24 January 2004 01:07, Chris W. Parker wrote: > on Friday, January 23, 2004 8:54 AM said: > > All of what you say makes sense. Hopefully your suggestion will help > > me find the problem! > > In looking through my code I see that I already do this. EVERY call to a > mysql function has "or die($this->stop("$current_line:".__LINE__));" > along with the call. $this->stop() is method that prints out > mysql_errno(); and mysql_error();. > > In this case the "or die" is not even being tripped meaning there isn't > an error. I'm beginning to think it's a bug, but it's more likely that > it's not. > > Here's another bit of crazy to throw in. The function I am trying to > perform is that of adding a record to my db. Guess what? The record > insertion is successul each time. And no I'm not closing the resource/db > link before those two functions are called. They happen immediately > after the the mysql_query() function. > > Sounds pretty fishy.... Time to put the php debugger in action -- echo all your variables to see that contain what you expect them to contain. -- Jason Wong -> Gremlins Associates -> www.gremlins.biz Open Source Software Systems Integrators * Web Design & Hosting * Internet & Intranet Applications Development * ------------------------------------------ Search the list archives before you post http://marc.theaimsgroup.com/?l=php-general ------------------------------------------ /* An expert is the person who avoids the small errors while sweeping on to the grand fallacy -- Thoreau's Theories of Adaption n1 */