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.
We all know that parameterized SQL is the way to go when dealing with user input and dynamic SQL, but is casting from string to int (or double, or long, or whatever) as effective if the input you are seeking is numeric?
I guess what I am asking is if this technique alone is infallible in regards to SQL injection?
I’m no expert, but I’m reasonably sure that this would be safe.
But why take the chance? Use parameterised SQL and you don’t ever need to worry about it.
Besides, parameterising your SQL has other advantages, not just injection-protection.