[teiid-issues] [JBoss JIRA] (TEIID-5281) Issue with concatenating null strings with OData translator

[Steven Hawkins (JIRA)]

    [ https://issues.jboss.org/browse/TEIID-5281?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13544739#comment-13544739 ] 

Steven Hawkins commented on TEIID-5281:
---------------------------------------

[~jmartisk] This doesn't seem to be mandated by odata, and I don't see the same behavior against the reference service.  Can you provide a full picture about everything involved - presumably this is an odata4 translator hitting an odata4 service exposed by Teiid, but which backend are you hitting?

> Issue with concatenating null strings with OData translator
> -----------------------------------------------------------
>
>                 Key: TEIID-5281
>                 URL: https://issues.jboss.org/browse/TEIID-5281
>             Project: Teiid
>          Issue Type: Bug
>          Components: OData
>    Affects Versions: 8.12.11.6_4
>            Reporter: Jan Martiska
>            Assignee: Steven Hawkins
>            Priority: Minor
>
> There is a difference in behavior of {{CONCAT(x,y)}} function in Teiid SQL and the {{concat(x,y)}} filtering function in OData - the SQL function will return null if one of the arguments is null, but the OData function will return the non-null argument in this case.
> This leads to some peculiar behavior that for rows where A='10' and B=null, the query
> {noformat}
> SELECT concat(A, B) = '10' 
> FROM BQT1.SmallA 
> WHERE concat(A, B) = '10';
> {noformat}
> will return a row containing {{false}}, because the expression in the SELECT clause will be evaluated by Teiid, whereas the one in the WHERE clause will be evaluated by the OData {{concat}} function.
> This is against the documented behavior of Teiid's {{CONCAT}} function, because such row should not be returned at all.



--
This message was sent by Atlassian JIRA
(v7.5.0#75005)