Eclipse Community Forums: EclipseLink » NOT operator is not handled properly in EclipseLink 2.4.0

Home » Eclipse Projects » EclipseLink » NOT operator is not handled properly in EclipseLink 2.4.0(NOT operator has wrong priority in 2.4.0)

Show: Today's Messages :: Show Polls :: Message Navigator

NOT operator is not handled properly in EclipseLink 2.4.0 [message #885707]

Wed, 13 June 2012 13:13

Nikolay Alexiev

Messages: 2
Registered: July 2009

Junior Member

Hello,

today I migrated to EclipseLink 2.4.0-RC2 and all my queries stopped working.
After investigating the issue, I found out that some of the conditions in my JPQL queries are not generating the correct SQL.

Here is a simplified example.

I have the following JPQL conditions:

(NOT( 1 = :free) OR v.price = 0)

(
 NOT(1 = :blockUnrated) OR 
 (...)
)

Using EclipseLink 2.3.1 I get the following SQL conditions:

(Not ((1 = ?)) Or (T0.Price = ?))

(Not ((1 = ?)) Or ...)

With EclipseLink 2.4.0 the SQL is wrong:

NOT (((1 = ?) OR (t0.PRICE = ?)))

NOT (((1 = 0) OR (....)))

As you can see in 2.4.0 the whole internal statement (OR) is inverted. Since NOT is a unary operator, it has a higher priority than anything else.

I am not sure if I'm wrong or this is a real bug. But in any case there's a big difference in behavior between 2.3.1 and 2.4.0.

It will be great if someone can test this and see if this is a real issue.

Report message to a moderator

Re: NOT operator is not handled properly in EclipseLink 2.4.0 [message #889714 is a reply to message #885707]

Tue, 19 June 2012 13:57

James Sutherland

Messages: 1939
Registered: July 2009
Location: Ottawa, Canada

Senior Member

Please log a bug for this issue and vote for it.

You can revert 2.4 to the old JPQL parser using the persistence unit property,

"eclipselink.jpql.parser"="ANTLR"

James : Wiki : Book : Blog : Twitter

Report message to a moderator