Tips for coders vol. 2
 

When writing MySQL queries try to make sure you can spot the difference between a comma and a semi-colon, so that you don't spend an hour shouting at the screen and end up going "NO I HAVEN'T got a FUCKING error in my FUCKING syntax you USELESS PIECE OF UTTER FUCKING SHI........oh wait, yes I have".

#1064 is the worst error code 😂

This was me for the past week, missed one fucking line and couldn't figure out why things weren't working. :upsidedow

Well, let me give you pro tip - you can use command php -l for syntax errors and it tells you exact line where you have error. So i dont have such problems ever.

Mine wasn't syntax, though, I just forgot a line completely, so no debugging or color coded editors helped :upsidedow

That doesn't tell you about SQL syntax errors inside a MySQL query string. MySQL does, but it can sometimes be a bit vague about where it is, but it does help if you realize that you are not infallible and you do make typos and it's not the computer being stupid :1orglaugh

That can be debugged easily too, copy paste your query, insert bogus data, and see what is mysql telling you. Tho you do have a point, very often things like ' " etc can fuck up query.