Programmer: Hey, man! What did you do to the database?
Jack: Nothing… Only an update for a client who asked to change the role of an user
Programmer: Uh… And by chance did you change his level to 4?
Jack: That’s right. Did you see that in the logs?
Programmer: No! You forgot the WHERE on UPDATE!!! All users are level 4 now!
Jack: Nothing… Only an update for a client who asked to change the role of an user
Programmer: Uh… And by chance did you change his level to 4?
Jack: That’s right. Did you see that in the logs?
Programmer: No! You forgot the WHERE on UPDATE!!! All users are level 4 now!
Programmer: Hey, man! What did you do to the database?
Jack: Nothing… Only an update for a client who asked to change the role of a user
Programmer: Uh… And by chance you did you change his level to 4?
Jack: That’s right. Did you see that in the logs?
Programmer: No! You forgot the WHERE on UPDATE!!! All users are level 4 now!
Been there … done that …
Now I just love Transactions ….
Grammer correction: “an user” is incorrect; it should be “a user”.
wait til you do it with the password column
please do something with the site and the facebook “like”-button, ’cause it posts wrong to the wall. With wrong picture (the portuguese flag), and wrong content “You may use these HTML tags and attributes:”
thanks
*Shudder*
Hate it when that happens. Best reason to never attempt a quick-fix on a production server
Too true, too true.
Queries…
I hate them
Could have been worse… when the user table gets dropped!
Been there, done that. Client had a backup.
One really shouldn’t be adjusting user security roles by directly inputting raw SQL statements. Mr. Programmer needs to write an interface.
the one with no hair represents the boss, right?
it must be…
I do that very often, have to learn w/ programmerslife :p
Ahhh!!! I am sure anyone who’s been programming for a while has done it once in his/her lifetime!