[
https://issues.jboss.org/browse/TEIID-4893?page=com.atlassian.jira.plugin...
]
Steven Hawkins updated TEIID-4893:
----------------------------------
Component/s: JDBC Connector
(was: Query Engine)
Priority: Critical (was: Blocker)
Or we should know that the SUBSTRING function works on teiid only by
this way and that's all?
The core problem is with using a non-positive index. Since substring and the associated
source functions aren't standard, there isn't consistent handling. We do though
assume that the Teiid behavior is the defacto correct behavior and translator logic when
possible should compensate. In this case the postgres translator is not accounting for
0/negative indexes and should be updated to account for that.
In general use 1 based indexing in string functions when possible.
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)