JDBC connection can use classpath

Documentation claims that the JDBC reader will work if the jar file is included in the CLASSPATH. This only worked if classpath was included in the .sql file but left empty. Leaving out the classpath setting resulted in NULL being passed to the JDBC connection and throwing an error. It makes sense to me that if the jar file is already included in CLASSPATH then requiring an empty classpath in the .sql file is redundant.