chemistry-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jens Hübel (JIRA) <j...@apache.org>
Subject [jira] Commented: (CMIS-212) opencmis CMISQL grammar is not standard compliant
Date Mon, 31 May 2010 21:25:39 GMT

    [ https://issues.apache.org/jira/browse/CMIS-212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12873789#action_12873789
] 

Jens Hübel commented on CMIS-212:
---------------------------------

Feedback:
Extensions are useful to have, for some repositories easy to implement. Duplication of grammar
for extension is considered to be a bad solution.
Extensions outside of standard should be clearly marked. A query implementation that strictly
follows the standard should not have to deal with the extensions

Suggestion:
Use two grammar files, one that follows the standard, one containing the extensions. Use this
mechanism for overriding the base grammars with extensions:  
http://www.antlr.org/wiki/display/ANTLR3/Composite+Grammars
This needs further investigation (has limitations, version dependency, maven integration,
etc.)



> opencmis CMISQL grammar is not standard compliant
> -------------------------------------------------
>
>                 Key: CMIS-212
>                 URL: https://issues.apache.org/jira/browse/CMIS-212
>             Project: Chemistry
>          Issue Type: Bug
>          Components: opencmis-server
>            Reporter: Jens Hübel
>            Assignee: Jens Hübel
>
> Our antlr grammar is not compliant to CMIS 1.0:
> 1)
> DISTINCT is not allowed as keyword in CmisSQL
> 2)
> The rule "string value function" is no longer supported. It existed in earlier versions
of the spec  but was removed. The grammar in our code does not reflect this change in the
specification.
> 3)
> only allowed operator with any is "=".  The rule "quantified comparison predicate" was
changed in the spec from allowing multiple comparison operators to only allow "=".  The grammar
in our code does not reflect this change in the specification.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message