Bug 1203128
| Summary: | Different null ordering for float and double numbers with RADIANS function (Oracle 12) | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [JBoss] JBoss Data Virtualization 6 | Reporter: | Juraj Duráni <jdurani> | ||||||
| Component: | Teiid | Assignee: | Van Halbert <vhalbert> | ||||||
| Status: | CLOSED WONTFIX | QA Contact: | |||||||
| Severity: | unspecified | Docs Contact: | |||||||
| Priority: | unspecified | ||||||||
| Version: | 6.1.0 | CC: | atangrin, vhalbert | ||||||
| Target Milestone: | --- | ||||||||
| Target Release: | --- | ||||||||
| Hardware: | x86_64 | ||||||||
| OS: | Linux | ||||||||
| Whiteboard: | |||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2015-05-01 15:50:23 UTC | Type: | Bug | ||||||
| Regression: | --- | Mount Type: | --- | ||||||
| Documentation: | --- | CRM: | |||||||
| Verified Versions: | Category: | --- | |||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||
| Embargoed: | |||||||||
| Attachments: |
|
||||||||
Created attachment 1003091 [details]
Server log for oracle10
Steven Hawkins <shawkins> updated the status of jira TEIID-3388 to Resolved Per engineering, this has been rejected as not an issue: 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 Steven Hawkins <shawkins> updated the status of jira TEIID-3388 to Closed |
Created attachment 1003090 [details] Server log for oracle 12 Description of problem: 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. Steps to Reproduce: Queries: - SELECT RADIANS(DoubleNum) FROM BQT1.SmallA ORDER BY DoubleNum; - SELECT RADIANS(FloatNum) FROM BQT1.SmallA ORDER BY FloatNum; This problem occurs only with oracle 12. Oracle 10/11/11RAC are fine. Source oracle databases (oracle 12 vs. oracle10): Source-float-column and source-double-colum have same types in both databases: FloatNum - float, DoubleNum - number. If you will not be able to reproduce it I can privately provide static VDB and datasource. Document URL: Section Number and Name: Describe the issue: Suggestions for improvement: Additional information: