SQL - solved; cron - unsolved

Well the SQL problem has been solved - the varchar needed a size. So now it has (255) added to it. Ran into a couple more problems before I was done. MySQL 4.0.x doesn’t support a BOOLEAN data type so I used CHAR(1). Yeah - I could have used an INT or enum(’T', ‘F’) but enum isn’t supported by all DB structures and a non-computer person will never remember that 1 = TRUE and 0 = FALSE. Heck - the only reason I remember is because I have a little sticky note on my monitor that reminds me (and yes I sometimes can’t tell my left from my right). :)

The cron script is still in the air. The hosting service keeps asking me if I am using the correct username when accessing the DB. How can I not be when the script works perfectly fine in a browser? Have to keep reminding myself that it WILL work eventually.

del.icio.us:SQL - solved; cron - unsolved  digg:SQL - solved; cron - unsolved  furl:SQL - solved; cron - unsolved  reddit:SQL - solved; cron - unsolved

WordPress database error: [Table 'wp1_comments' is marked as crashed and last (automatic?) repair failed]
SELECT * FROM wp1_comments WHERE comment_post_ID = '111' AND comment_approved = '1' ORDER BY comment_date

Leave a Reply