There is a problem when using the MySQL-4 properties _emptyStringsConvertToZero_ and _jdbcCompliantTruncation_ together, i.e. are both set to "true".

We have migrated from MySQL 3 to 4 last time and now I am running into several problems, of course ;-). The most of them could be solved, but there is an inconsistency IMHO, which I have to report:

I want to use the new feature of throwing a java.sql.DataTruncation exception to create appropriate log information. This exception will also be thrown when empty strings are used for not-char columns (e.g. decimals like 'int(11)' etc.) in Insert or Update commands. Okay, I said to me, there is another database driver property called _emptyStringsConvertToZero_ which I can switch on. But it doesn't work as expected: the java.sql.DataTruncation exceptions are throwing further on :-( while the empty strings are treated correctly as '0'. Only when I set _jdbcCompliantTruncation_ to "false" it works, but behaves much like MySql 3 which I do not want to have ;-).

It seems to me that this could be a simple ordering problem. I.e. if the property _emptyStringsConvertToZero_ is set to "true" it has to be processed *before* checking truncation (if _jdbcCompliantTruncation_ is also "true").