You are viewing a plain text version of this content. The canonical link for it is here.
Posted to oak-issues@jackrabbit.apache.org by "Thomas Mueller (JIRA)" <ji...@apache.org> on 2017/04/27 12:28:04 UTC
[jira] [Commented] (OAK-5949) XPath: string literals parsed as
identifiers
[ https://issues.apache.org/jira/browse/OAK-5949?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15986493#comment-15986493 ]
Thomas Mueller commented on OAK-5949:
-------------------------------------
The fix is easy. Both for XPath and SQL-2, some invalid statements were accepted because double quotes were ignored. I hope applications didn't rely on this bug being there.
> XPath: string literals parsed as identifiers
> --------------------------------------------
>
> Key: OAK-5949
> URL: https://issues.apache.org/jira/browse/OAK-5949
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: query
> Reporter: Thomas Mueller
> Assignee: Thomas Mueller
> Priority: Critical
> Fix For: 1.8
>
>
> The following query (for example) is not parsed correctly, as {{@}} is parsed as attribute prefix:
> {noformat}
> /jcr:root/home//element(*,rep:Authorizable)[jcr:like(@rep:authorizableId,'@')]
> {noformat}
> Possibly XPathToSQL2Converter should use currentTokenQuoted for this. Possibly a similar problem can occur in SQL2Parser (needs to be tested). Right now, it looks like currentTokenQuoted is never set to true; that should probably happen in read().
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)