[ https://issues.jboss.org/browse/TEIID-3573?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-3573: --------------------------------------- IS NULL/IS NOT NULL is appropriate from the user query when you are explicitly testing for null. In this case we are not testing null, rather intNum <> 1. It's returning true for a null intNum - that is not expected with 3 valued SQL (but could be the result in 2 valued systems). Yes, if they are a 2 valued system, then we should change the translator logic to compensate. So if it sees where intNum<>1 it would need to produce "intNum<>1 and intNum IS NOT NULL". If that's not generally something that the translator can handle we can look at letting the engine compensate, but that could come with a lot of restrictions. -- This message was sent by Atlassian JIRA (v6.3.15#6346)