Re: JDBC, STRICT_TRANS_TABLES, & Null OUT Parameter Problem

[Jack Barney]

Follow up. I came across 2 other pieces of information at
http://www.lancs.ac.uk/ug/coole/APIs%20&%20Libraries/mysql-connector-java-5.1.10/docs/connector-j.html

jdbcCompliantTruncation: Should the driver throw java.sql.DataTruncation exceptions when data is truncated as is required by the JDBC specification when connected to a server that supports warnings (MySQL 4.1.0 and newer)? This property has no effect if the server sql-mode includes STRICT_TRANS_TABLES.

noAccessToProcedureBodies: When determining procedure parameter types for CallableStatements, and the connected user can't access procedure bodies through "SHOW CREATE PROCEDURE" or select on mysql.proc should the driver instead create basic metadata (all parameters reported as IN VARCHARs, but allowing registerOutParameter() to be called on them anyway) instead of throwing an exception?

This explains the string value 'null'; however, when the connection URL parameters have jdbcCompliantTruncation=false&noAccessToProcedureBodies=false set and the correct permissions are granted on mysql.proc and mysql.procs_priv, the sqlexception is still thrown.