if #1 is Not using bind variables will get you fired.

then #2 should be "you should be able to tell us when not using a bind variable is not only acceptable but preferred"


The general rule should be - definitely - use a bind. Unless you are perhaps a data warehouse application - whereby using a bind for the data warehouse queries (just those queries, not the rest of the lot) would be a bad thing in general (you want to spend an extra second parsing SQL when you have SQL that takes minutes or hours to execute).

here is the rest of the short list

#3 should be "you have read the concepts guide"

#4 you can describe what multi-version read consistency is and explain why you care

#5 you understand locking and concurrency control in the database

#6 you have undertaken steps to get as knowledgeable on SQL as you are in Java, and if not you shall relinquish all database access to someone that has

#7 stored procedures are not evil, in fact, they promote code reuse much more than java can and will, they are more maintainable, they are more portable, they will be around after your application is put to rest

#8 design counts, there are times when generic is good - but they are exceedingly rare, you will actually design your schemas (with help).