TEIID-4693 adding a note about tinyint(1) behavior

teiid · Jan 12, 2017 · d360e43 · d360e43
1 parent 406fbaf
commit d360e43
Showing 1 changed file with 4 additions and 1 deletion.
diff --git a/reference/MySQL_Translators.adoc b/reference/MySQL_Translators.adoc
@@ -26,4 +26,7 @@ set SESSION sql_mode = 'ANSI'
 
 If you may deal with null timestamp values, then set the connection property zeroDateTimeBehavior=convertToNull. Otherwise you’ll get conversion errors in Teiid that `0000-00-00 00:00:00' cannot be converted to a timestamp.
 
-WARNING: If retrieving large result sets, you should consider setting the connection property useCursorFetch=true, otherwise MySQL will fully fetch result sets into memory on the Teiid instance.
+WARNING: If retrieving large result sets, you should consider setting the connection property useCursorFetch=true, otherwise MySQL will fully fetch result sets into memory on the Teiid instance.
+
+NOTE: MySQL reports TINYINT(1) columns as a JDBC BIT type - however the value range is not actually restricted and may cause issues if for example you are relying on -1 being recognized as a true value.  
+If not using the native importer, you should change affected source BOOLEAN columns to have a native type of "TINYINT(1)" rather than BIT so that the translator can appropriately handle the boolean conversion.