[teiid-issues] [JBoss JIRA] Resolved: (TEIID-1341) boolean=true doesn't work predictably against MySQL connector

[Steven Hawkins (JIRA)]

     [ https://jira.jboss.org/browse/TEIID-1341?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Steven Hawkins resolved TEIID-1341.
-----------------------------------

    Fix Version/s:     (was: 7.3)
       Resolution: Rejected


I'm going to reject this issue.  The importer will not import a numeric type that is wider than a single bit as a boolean, so this will only occur if the user is changing physical types in the designer.  In general this is bad idea (as this issue demonstrates).  To properly handle this situation, a view should be added over the physical to perform the conversion from the numeric type to boolean, then the pushdown logic will account for non-0 values as true.  That is far simpler than adding more catch all logic in the translator.

> boolean=true doesn't work predictably against MySQL connector
> -------------------------------------------------------------
>
>                 Key: TEIID-1341
>                 URL: https://jira.jboss.org/browse/TEIID-1341
>             Project: Teiid
>          Issue Type: Quality Risk
>          Components: JDBC Connector
>    Affects Versions: 6.0.0
>            Reporter: Debbie Steigner
>
> MySQL defines false as zero and anything else as a true. So, in MySQL, writing "... where boolean_column = true ..." will usually not evaluate correctly because true is defined as one. To avoid this confusion, MMX should translate boolean_column=true to boolean_column<>false in the SqlTranslator of the MySQL Connector. 

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira