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/22 09:52:20 UTC

[jira] [Commented] (IGNITE-3716) ODBC: Implement escape sequence parsing.

    [ https://issues.apache.org/jira/browse/IGNITE-3716?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15430466#comment-15430466 ] 

Vladimir Ozerov commented on IGNITE-3716:
-----------------------------------------

It makes sense to start with scalar function replacement as it looks relatively simple to parse and process.

> ODBC: Implement escape sequence parsing.
> ----------------------------------------
>
>                 Key: IGNITE-3716
>                 URL: https://issues.apache.org/jira/browse/IGNITE-3716
>             Project: Ignite
>          Issue Type: Task
>          Components: odbc
>    Affects Versions: 1.7
>            Reporter: Vladimir Ozerov
>            Assignee: Andrew Mashenkov
>            Priority: Critical
>             Fix For: 1.8
>
>
> ODBC standard defines a set of special escape sequences [1] which help to create SQL requests in database-independent format. We need to implement special processor which will accept ODBC string and return parsed SQL query string.
> Possible simple stack-based approach:
> 1) When escape start is found, put it's start position into stack. 
> 2) If there are no other escapes between start and end - evaluate expression.
> 3) Finally, replace escape sequence in original string and adjust positions up the stack accordingly.
> This way after N replaces we will have fully-escape string.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)