in reply to Bitten by the lazy execution bug?

Are you sure the table only has the three columns you expect? In the right order? And will always have? Really?

I would not recomend using the "INSERT INTO TableName VALUES (...)" (or REPLACE INTO) form, specify the columns explicitely! You can never know when will someone reorder the columns or add some more and you end up with an error (if lucky) or invalid data.

Replies are listed 'Best First'.
Re^2: Bitten by the lazy execution bug?
by Anonymous Monk on Dec 08, 2007 at 18:10 UTC
    Actually, this is one of the steps I took ( I thought the columns may have been getting swaped around ), so I actually have been using the "explicit column name" version of insert/replace, but that also had no affect on the execution of the code. The only thing that seems to alter whether it runs or not is using the $3 variable prior to the do call.