Tips for coders vol. 2

Collapse
X
Collapse
 
  • Page of 1
  • Time
  • Show
Clear All
new posts
Previous template Next
  • redwhiteandblue
    Bollocks
    • Jun 2007
    • 2793
    #1

    Tech 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".
    Interserver unmanaged AMD Ryzen servers from $73.00
    Tags: None
    • k33n
      Confirmed User
      • Feb 2009
      • 201
      #2
      #1064 is the worst error code 😂

        Comment

        • Colmike9
          (>^_^)b
          • Dec 2011
          • 7230
          #3
          Originally posted by redwhiteandblue
          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".
          This was me for the past week, missed one fucking line and couldn't figure out why things weren't working.
          Join the BEST cam affiliate program on the internet!
          I've referred over $1.7mil in spending this past year, you should join in.
          I make a lot more money in the medical field in a lab now, fuck you guys. Don't ask me to come back, but do join Chaturbate in my sig, it still makes bank without me touching shit for years..

            Comment

            • Klen
              • Aug 2006
              • 32235
              #4
              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.

                Comment

                • Colmike9
                  (>^_^)b
                  • Dec 2011
                  • 7230
                  #5
                  Originally posted by Klen
                  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
                  Join the BEST cam affiliate program on the internet!
                  I've referred over $1.7mil in spending this past year, you should join in.
                  I make a lot more money in the medical field in a lab now, fuck you guys. Don't ask me to come back, but do join Chaturbate in my sig, it still makes bank without me touching shit for years..

                    Comment

                    • redwhiteandblue
                      Bollocks
                      • Jun 2007
                      • 2793
                      #6
                      Originally posted by Klen
                      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.
                      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
                      Interserver unmanaged AMD Ryzen servers from $73.00

                        Comment

                        • Klen
                          • Aug 2006
                          • 32235
                          #7
                          Originally posted by redwhiteandblue
                          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
                          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.

                            Comment

                            Previous template Next
                            Working...