[teiid-issues] [JBoss JIRA] (TEIID-3388) Different null ordering for float and double numbers with RADIANS function (Oracle 12)

[Steven Hawkins (JIRA)]

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

Steven Hawkins resolved TEIID-3388.
-----------------------------------
    Resolution: Rejected


The models are different between these two cases such that we'll push the order by for the ora 12 query, but not ora 10 (there is a conversion on floatnum for example that doesn't exist in ora 12).  In any case this results in the different null orderings as null ordering is not guaranteed unless you add a nulls first/last clause to the order key:

order by floatnum nulls first

See https://docs.jboss.org/author/display/TEIID/ORDER+BY+Clause

> Different null ordering for float and double numbers with RADIANS function (Oracle 12)
> --------------------------------------------------------------------------------------
>
>                 Key: TEIID-3388
>                 URL: https://issues.jboss.org/browse/TEIID-3388
>             Project: Teiid
>          Issue Type: Bug
>    Affects Versions: 8.7.1
>            Reporter: Juraj Duráni
>            Assignee: Steven Hawkins
>         Attachments: server_ora10.log, server_ora12.log
>
>
> Queries:
> 1. SELECT RADIANS(DoubleNum) FROM BQT1.SmallA ORDER BY DoubleNum;
> 2. SELECT RADIANS(FloatNum) FROM BQT1.SmallA ORDER BY FloatNum;
> Both queries return different null ordering. In case of DoubleNum nulls are first. In the second case nulls are last records.



--
This message was sent by Atlassian JIRA
(v6.3.11#6341)