You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Vladimir Ozerov (JIRA)" <ji...@apache.org> on 2016/08/24 10:06:20 UTC
[jira] [Updated] (IGNITE-3738) ODBC: Escape sequences: Ensure that
escape sequence token is parsed correctly irrespective of whitespaces.
[ https://issues.apache.org/jira/browse/IGNITE-3738?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Vladimir Ozerov updated IGNITE-3738:
------------------------------------
Summary: ODBC: Escape sequences: Ensure that escape sequence token is parsed correctly irrespective of whitespaces. (was: ODBC: Escape functions: Ensure that escape sequence token is parsed correctly irrespective of whitespaces.)
> ODBC: Escape sequences: Ensure that escape sequence token is parsed correctly irrespective of whitespaces.
> ----------------------------------------------------------------------------------------------------------
>
> Key: IGNITE-3738
> URL: https://issues.apache.org/jira/browse/IGNITE-3738
> Project: Ignite
> Issue Type: Sub-task
> Components: odbc
> Affects Versions: 1.7
> Reporter: Vladimir Ozerov
> Assignee: Andrew Mashenkov
> Fix For: 1.8
>
>
> The following escape sequences must be supported and parsed correctly:
> 1) {fn X}
> 2) { fn X}
> 3) { fn X}
> 4) { \n X}
> Etc. That is, irrespective of whitespaces, everything must be parsed correctly. I propose to rely on {{Character.isWhitespace}}, not on regexp. That is, once { is found, we should simply skip all following whitespaces, then get the token, then possibly skip more whitespaces.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)