Prefer PreparedStatement

PreparedStatement is usually preferred over Statement for these reasons:

In general, it seems safest to use a Statement only when the SQL is of fixed, known form, with no parameters.

SQL Injection

If PreparedStatement is used correctly, then it does indeed provide complete protection against SQL Injection attacks. However, if it's used incorrectly, then it's still wide open to such attacks.

The SQL statement passed to PreparedStatment is simply an unvalidated String, in the sense that there's no checking for '?' values. If the String has been constructed using '?' placeholders for all dynamic data, then it has indeed been constructed correctly.

But PreparedStatement has no built-in mechanism to prevent the inexperienced or inattentive programmer from passing a String which, by mistake, does not always use a '?' placeholder where it should. Such Strings are wide open to SQL Injection attacks.

See Also :
Keep SQL out of code
Beware of common hacks
Would you use this technique?
Yes   No   Undecided   
© 2014 Hirondelle Systems | Source Code | Contact | License | RSS
Individual code snippets can be used under this BSD license - Last updated on September 21, 2013.
Over 2,000,000 unique IPs last year - Built with WEB4J.
- In Memoriam : Bill Dirani -