[teiid-issues] [JBoss JIRA] (TEIID-4656) parseTimestamp issue with Oracle

Steven Hawkins (JIRA) issues at jboss.org
Wed Dec 21 17:01:00 EST 2016


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

Steven Hawkins resolved TEIID-4656.
-----------------------------------
    Resolution: Done


This behavior looks correct.  Parsetime is not being pushed - in the pushdown query you can see nested converts, not the parsetime function.  The translator handling of a string column to a time time is to_char with the expected time format.  The exception should mean that the string column is not correctly formatted as a time value.

> parseTimestamp issue with Oracle
> --------------------------------
>
>                 Key: TEIID-4656
>                 URL: https://issues.jboss.org/browse/TEIID-4656
>             Project: Teiid
>          Issue Type: Bug
>          Components: JDBC Connector, Query Engine
>    Affects Versions: 8.12
>            Reporter: Steven Hawkins
>            Assignee: Steven Hawkins
>             Fix For: 8.7.10.6_2, 9.2
>
>
> parseTimestamp is pushed as to_timestamp.  However TO_TIMESTAMP is not generally valid unless the format string covers the entire string input value otherwise there is an exception about the picture ending.  
> This means in general that we cannot pushdown the parseDate/Time/Timestamp operations to oracle as that is behavioral different with the java format routines, which will process just to the end of the format string.  



--
This message was sent by Atlassian JIRA
(v7.2.3#72005)


More information about the teiid-issues mailing list