You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@olingo.apache.org by "Chandan V.A (JIRA)" <ji...@apache.org> on 2014/11/01 08:16:34 UTC
[jira] [Created] (OLINGO-478) Operator Precedence ignored
Chandan V.A created OLINGO-478:
----------------------------------
Summary: Operator Precedence ignored
Key: OLINGO-478
URL: https://issues.apache.org/jira/browse/OLINGO-478
Project: Olingo
Issue Type: Bug
Components: odata2-jpa
Affects Versions: V2 2.0.1
Reporter: Chandan V.A
Assignee: Chandan V.A
-----Original Message-----
From: Giacomo Pati [mailto:giacomo@pati.ch]
Sent: Freitag, 31. Oktober 2014 08:41
To: dev@olingo.apache.org
Subject: Serious bug in FilterParser
Hi all
We recently run into a serious issue regarding filters and I want someone
of you to double check. When you run the following query against a
deployed olingo-odata2-jpa-processor-ref-web
like
http://localhost:8080/SalesOrderProcessing.svc/SalesOrderItems?$filter=(SoId
eq 2 or SoId eq 3 or SoId eq 4) and Delivered eq true
one would expect to see only Entities with a property Delivered == true but
this is not the case. I've also run a quick junit test against
FilterParserImpl with such a query using an ExpressionVisitor and figured
that it seems that the parenthesis are not respected which would reduce the
query to "SoId eq 2 or SoId eq 3 or SoId eq 4 and Delivered eq true" and it
seems that is actually what happens.
Anyone else?
Ciao
--
Giacomo
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)