[JBoss JIRA] (TEIID-4893) Inconsistent behavior of SUBSTRING function
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-4893?page=com.atlassian.jira.plugin... ]
Steven Hawkins resolved TEIID-4893.
-----------------------------------
Fix Version/s: 9.3
9.1.5
9.2.3
Resolution: Done
Added rewrite logic and updated the postgresql translator to match the behavior of the teiid substring function.
> Inconsistent behavior of SUBSTRING function
> -------------------------------------------
>
> Key: TEIID-4893
> URL: https://issues.jboss.org/browse/TEIID-4893
> Project: Teiid
> Issue Type: Bug
> Components: JDBC Connector
> Affects Versions: 9.0.3
> Environment: teiid-9.0.3 on WildFly Full 9.0.2.Final (WildFly Core 1.0.2.Final)
> Reporter: dalex dalex
> Assignee: Steven Hawkins
> Priority: Critical
> Fix For: 9.3, 9.1.5, 9.2.3
>
>
> There is inconsistent behavior of SUBSTRING function in teiid and data sources.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 8 months
[JBoss JIRA] (TEIID-2711) Better support for Oracle SQLXML values
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-2711?page=com.atlassian.jira.plugin... ]
Steven Hawkins resolved TEIID-2711.
-----------------------------------
Resolution: Done
Added a doc note to cover the general case of getting a SQLXML value. The code change is unlikely to be needed given the time this was open and not seen as an issue.
> Better support for Oracle SQLXML values
> ---------------------------------------
>
> Key: TEIID-2711
> URL: https://issues.jboss.org/browse/TEIID-2711
> Project: Teiid
> Issue Type: Quality Risk
> Components: JDBC Connector
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Fix For: 9.3
>
> Attachments: oracle.patch
>
>
> When using a typical driver configuration to read oracle xml values, the driver will return an OPAQUE instance rather than a SQLXML value.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 8 months
[JBoss JIRA] (TEIID-4893) Inconsistent behavior of SUBSTRING function
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-4893?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-4893:
---------------------------------------
Yes, the current function modifier just translates into substring(val from x [, for y]). It's possible to update that into a case statement instead that handles the 0 and negative cases as well.
> Inconsistent behavior of SUBSTRING function
> -------------------------------------------
>
> Key: TEIID-4893
> URL: https://issues.jboss.org/browse/TEIID-4893
> Project: Teiid
> Issue Type: Bug
> Components: JDBC Connector
> Affects Versions: 9.0.3
> Environment: teiid-9.0.3 on WildFly Full 9.0.2.Final (WildFly Core 1.0.2.Final)
> Reporter: dalex dalex
> Assignee: Steven Hawkins
> Priority: Critical
>
> There is inconsistent behavior of SUBSTRING function in teiid and data sources.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 8 months
[JBoss JIRA] (TEIID-4849) Google translator behaves unexpectedly with Double in WHERE clause of SELECT
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-4849?page=com.atlassian.jira.plugin... ]
Steven Hawkins resolved TEIID-4849.
-----------------------------------
Fix Version/s: (was: 10.0)
Resolution: Rejected
After reviewing this in light of TEIID-4854, this is not an issue. For the read case the user's worksheet can be in any locale - it is not expected that the values are formatted to SQL/Teiid literals. As long as the column is recognized as numeric, then the Teiid user query will work as expected.
> Google translator behaves unexpectedly with Double in WHERE clause of SELECT
> ----------------------------------------------------------------------------
>
> Key: TEIID-4849
> URL: https://issues.jboss.org/browse/TEIID-4849
> Project: Teiid
> Issue Type: Feature Request
> Components: Misc. Connectors
> Affects Versions: 8.12.10.6_3
> Reporter: Lucie Fabrikova
> Priority: Minor
>
> Query like "SELECT DoubleNum FROM SmallA WHERE DoubleNum > 5.0" gives unexpected results for following values in DoubleNum column:
> * value like '15.1' is probably by google spreadsheet interpreted as date (in function row in sheet appears 15.1.2017), SELECT query returns no results
> * value like '150.1': SELECT returns null
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 8 months