[ https://issues.jboss.org/browse/TEIID-586?page=com.atlassian.jira.plugin.... ] Steven Hawkins commented on TEIID-586: -------------------------------------- I may defer this until it is hit as an issue, and just add a KI with the workaround to specify SIMILAR or a REGEX LIKE which would not be supported by the source (although for performance you would want partial matching pushed down as mentioned in the description). Another option would be to disable the like support by default for ldap and salesforce and add a pushdown function to represent the native like handling - e.g. ldap.match(col, 'a*b') Generally speaking there we have an issue with any string comparison including like on any database when the column is using an alternative collation (including ones that are case insensitive) - as the results may not match Teiid's. As our metadata system is too rigid/class based, we'd have to introduce a different value holder for strings that included the collation. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira