On a table where user_id is INT
Why is:
SELECT * FROM tableName where user_id = 63
recommended instead of
SELECT * FROM tableName where user_id = '63'
On a table where user_id is INT Why is: SELECT * FROM tableName where
Share
Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
On a table where user_id is INT
Why is:
SELECT * FROM tableName where user_id = 63
recommended instead of
SELECT * FROM tableName where user_id = '63'
In some cases at least in former mysql versions sometimes it happened that mysql casted left part of expression (the column) to the string, not the right to an integer.
This lead to unexpected fullscan, instead of using indexes.
I don’t even mention that it just makes no sense.