Page 1 of 1

I was about to murder somebody until...

Posted: Mon Oct 16, 2006 1:38 pm
by Luke
I found out that the reason I have been pulling my hair out wanting to scream at the top of my lungs at the stupid computer was due to not selecting a database before trying to use it... I am a moron... a very angry moron... :evil: :x :?

EDIT: I just had to let somebody know... because this is the most angry I had ever been at code in my life... I was about to seriously kill somebody. Project is supposed to be done by next week and this stupid bug was driving me INSANE!

But I'm cool now... 8)

Posted: Mon Oct 16, 2006 1:50 pm
by feyd
Heh, such a simple bug. It's easy to overlook the simple errors and think it's something complicated or "odd."

Posted: Mon Oct 16, 2006 1:53 pm
by Ollie Saunders
I was going mad at array_map and array_walk a while back. One of them modifies by reference and the other returns and also the parameters differ.
It's easy to overlook the simple errors and think it's something complicated or "odd."
Very true.
I've started keeping a diary of bugs now.

Posted: Mon Oct 16, 2006 1:57 pm
by John Cartwright
ahem, mysql_error() :wink:

Posted: Mon Oct 16, 2006 2:10 pm
by RobertGonzalez
Uh, I have never done that 8).

/me, looks the other way quickly so as not to show the blatant lie screaming out of my eyes...

Posted: Mon Oct 16, 2006 2:13 pm
by MrPotatoes
dude the simplest errors are the worst but the best when you figure it out.

for instance, when some of my buddies were coding i would open up a file, #define e 0 (making anything with an e in code mean 0) then save and close it. then give them a half hour wondering with them what was wrong.

then 1/2 hour later i'd tell them. those were the good ole days

*sigh*

Posted: Mon Oct 16, 2006 2:41 pm
by Luke
Jcart wrote:ahem, mysql_error() :wink:
lol yea... I kept using $Mysql->getError() and never checked to make sure that Mysql->getError returned mysql_error()... and it didn't.