DB coding

May 25, 2006 23:50

Remember kids...when working with a database, entering the command "Update table set = " is probably a bad idea. A much better idea is to enter: "update table set = where like "

*sigh*...almost 2500 entries (which at the time of this writing is the entire table) corrupted because I did the first and not the second....to borrow a phrase from

fubar, programming

Leave a comment

Comments 2

skywalker404 May 30 2006, 23:42:17 UTC
Yeah, I've learned to build my queries in such a way that they're not runnable until I'm finished, they won't have an effect until I change them to an update/insert, or to build them in notepad. Yeesh.

Reply

clayemore May 31 2006, 06:38:18 UTC
It was easier to fix than I thought it would be....since I know the number of tuples for each "subtable" (or set of cards) I just iterated through the table changing the set back to what it should be. Took me maybe half an hour...

Reply


Leave a comment

Up