[
https://issues.apache.org/jira/browse/CALCITE-2653?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16674711#comment-16674711
]
winifredtang edited comment on CALCITE-2653 at 11/5/18 6:30 AM:
----------------------------------------------------------------
You are right, it's my mistake, 'SUBSTRING' may be Case Sensitive? We used
'substring' which has made us got this exception. When we changed it to
'SUBSTRING(NAME FROM 2)', there was no exception any more.
was (Author: winipanda):
You are right, it's my mistake, 'SUBSTRING' is Case Sensitive. We used
'substring' which has made us got this exception. Thank you so much.
> Correct the operator syntax of String Function SUBSTRING in reference.md
> ------------------------------------------------------------------------
>
> Key: CALCITE-2653
> URL: https://issues.apache.org/jira/browse/CALCITE-2653
> Project: Calcite
> Issue Type: Improvement
> Components: site
> Affects Versions: 1.17.0
> Reporter: winifredtang
> Assignee: Julian Hyde
> Priority: Minor
>
> I wonder if we can change the operator syntax of String Function SUBSTRING
> from SUBSTRING(string FROM integer) to SUBSTRING(string, integer). Since it
> might be a bit of misleading.
> Executing a SQL statement like "select substring(name FROM 2) from
> sales.depts;" would throw a exception :
> "Caused by: org.apache.calcite.sql.parser.impl.ParseException: Encountered
> "select" at line 2, column 1."
> The correct SQL statement is "select substring(NAME,2) from sales.depts;".
> SUBSTRING(string FROM integer FOR integer) has the same promble.
> If necessary, I'd like to modify it.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
