A couple of years ago I began developing in Java, and my first Java project
required that I also learn SQL. Our project team was using mostly EJBs for
database access, although for some performance-critical sections of the
application we wrote the JDBC logic directly. A problem that we faced
regularly was tracking the bind parameters to our PreparedStatements. Over
the course of the project, all of the team members tried different techniques
to determine what our JDBC statements were actually doing.
This article presents a solution that one of the developers created to help
solve this problem. I took his original idea and extended it after I left
that team to help my next company solve the same problem. The solution is a
JDBC driver that uses log4j to print all SQL state... (more)