DataNucleus JIRA is now in read-only mode. Raise any new issues in GitHub against the plugin that it applies to. DataNucleus JIRA will remain for the foreseeable future but will eventually be discontinued
Issue Details (XML | Word | Printable)

Key: NUCCORE-412
Type: Bug Bug
Status: Closed Closed
Resolution: Fixed
Priority: Minor Minor
Assignee: Andy Jefferson
Reporter: Andy Jefferson
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
DataNucleus Core

Generic compilation : Compilation of JPQL "NOT" is being applied to the next identifier rather than boolean expression

Created: 20/Oct/09 01:48 PM   Updated: 23/Oct/09 04:07 PM   Resolved: 20/Oct/09 01:58 PM
Component/s: Queries
Affects Version/s: 2.0.0.m1, 2.0.0.m2
Fix Version/s: 2.0.0.m3


 Description  « Hide
When we have a WHERE clause like
NOT o.totalPrice < 4500

this is being compiled as
DyadicExpression
{
    DyadicExpression
    {
        PrimaryExpression{o.totalPrice}
        NOT
        null
    }
    <
    Literal{4500}
}

yet really it ought to be
NOT (o.totalPrice < 4500)

but then there are ample workarounds etc, like expressing the syntax clearly

Sort Order: Ascending order - Click to sort in descending order
Andy Jefferson added a comment - 20/Oct/09 01:58 PM
SVN trunk now applies NOT to the next relational expression