Mailing-List: contact dev-help@jackrabbit.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@jackrabbit.apache.org
Message-ID: <24346295.1162305138888.JavaMail.root@brutus>
Date: Tue, 31 Oct 2006 06:32:18 -0800 (PST)
From: "Jukka Zitting (JIRA)" <jira@apache.org>
To: dev@jackrabbit.apache.org
Subject: [jira] Updated: (JCR-562) 'OR' in XPath query badly interpreted
In-Reply-To: <9582064.1157526082360.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

     [ http://issues.apache.org/jira/browse/JCR-562?page=all ]

Jukka Zitting updated JCR-562:
------------------------------

          Component/s: xpath
                           (was: core)
        Fix Version/s: 1.1.1
    Affects Version/s: 0.9
                       1.0
                       1.1

> 'OR' in XPath query badly interpreted
> -------------------------------------
>
>                 Key: JCR-562
>                 URL: http://issues.apache.org/jira/browse/JCR-562
>             Project: Jackrabbit
>          Issue Type: Bug
>          Components: xpath
>    Affects Versions: 1.0, 1.0.1, 1.1, 0.9
>            Reporter: Szymon Kuzniak
>             Fix For: 1.1.1
>
>         Attachments: JCR-562.patch, tree.JPG
>
>
> executing query: //*[@a=1 and @b=2 or @c=3] leads to creating wrong query tree. The builded tree looks like for query: //*[@a=1 and @b=2 and @c=3](see attachement). using brackets resolves the problem, but without brackets output query is different from input query. When AND and OR are switched(so the OR is in first palce - //*[@a=1 or @b=2 and @c=3]) everything is ok.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira