You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@jackrabbit.apache.org by "Christian Kalkhoff (JIRA)" <ji...@apache.org> on 2015/09/30 14:47:04 UTC

[jira] [Created] (JCR-3911) Precedence error with AND NOT in JCQ-SQL2

Christian Kalkhoff created JCR-3911:
---------------------------------------

             Summary: Precedence error with AND NOT in JCQ-SQL2 
                 Key: JCR-3911
                 URL: https://issues.apache.org/jira/browse/JCR-3911
             Project: Jackrabbit Content Repository
          Issue Type: Bug
            Reporter: Christian Kalkhoff


Querying the repository shows an at least unexpected behaviour.

running 

SELECT * FROM [[my:type]] WHERE ISDESCENDANTNODE('/foo/bar') AND prop1 = 'foo' AND prop2 = 'bar' AND NOT prop3 = '' AND prop4 = 'jazz'

will return all nodes that match prop1, prop2, prop3 but prop4 is ignored. So how far i can tell the NOT in AND NOT catches somehow the rest of the constraint. The spec seams to be unclear about it, from RDBMS' SQL i would say the behaviour is non-standard.



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