Long.MIN_VALUE is parsed incorrectly in a query

[ErikShiken]

OrientDB Version: 2.2.29

Java Version: 1.8.0_72

OS: Windows 10

Expected behavior

Parse Long.MIN_VALUE correctly for a query

Actual behavior

Parser throws an exception

Steps to reproduce

Use a query that check the value of a property using Long.MIN_VALUE
For example:
SELECT FROM V WHERE hs_3apoint >= -9223372036854775808

It appears the '-' is parsed first and then the number. Since 9223372036854775807 is the max long value, a parsing exception occurs.

[luigidellaquila]

Hi @ErikShiken

Thank you very much for reporting, I'm checking it now

Thanks

Luigi

[luigidellaquila]

hi @ErikShiken

I just pushed a fix to develop branch (3.0.x), it will be released with v 3.0.4

Now I'm backporting it to v 2.2.x

Thanks

Luigi