[jira] [Comment Edited] (OPTIQ-321) Allow library users to replace implementation of CompoundIdentifier in SQL Parser

["Julian Hyde (JIRA)" <ji...@apache.org>]

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

Julian Hyde edited comment on OPTIQ-321 at 7/3/14 12:23 AM:
------------------------------------------------------------

I think in that case even the base parser should generate calls to the dot operator.

There are uses of {{CompoundIdentifier()}} outside of scalar expressions -- e.g. {{INSERT INTO CompoundIdentifier() ...}} -- and I think these should remain. But an expression, e.g. e.name, should be parsed as {{SqlCall(DOT, SqlIdentifier("e"), SqlIdentifier("name"))}}. And then the validator should figure out what the DOT means.


was (Author: julianhyde):
I think in that case even the base parser should generate calls to the dot operator.

There are uses of CompoundIdentifier outside of scalar expressions -- e.g. {INSERT INTO CompoundIdentifier() ...} -- and I think these should remain. But an expression, e.g. e.name, should be parsed as SqlCall(DOT, SqlIdentifier("e"), SqlIdentifier("name")). And then the validator should figure out what the DOT means.

> Allow library users to replace implementation of CompoundIdentifier in SQL Parser
> ---------------------------------------------------------------------------------
>
>                 Key: OPTIQ-321
>                 URL: https://issues.apache.org/jira/browse/OPTIQ-321
>             Project: Optiq
>          Issue Type: Improvement
>            Reporter: Jacques Nadeau
>            Assignee: Jacques Nadeau
>
> This will allow users to support alternative identifier constructs.



--
This message was sent by Atlassian JIRA
(v6.2#6252)