You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@anidotnet I compared the implementations of apply in EqualsFilter.java and LesserEqualFilter.java and once I discovered this section, it seemed clear that this is part of the problem.
After all, the check for instanceof Number is specifically a recognition that different subclasses are still directly comparable. I wrote a little unit test locally based on @enitram's repro snippet above and I confirmed that commenting out lines 130-132 causes the first assert to no longer fail. 🎉 (Of course, it does make a few other tests elsewhere in the project fail, and now I'm out of my depth on the internal logic of Nitrite's filter abstractions.)
When comparing numbers of different types, nitrite returns different results depending on the filter (eq, lte, gte) and if the value was indexed.
Here is a small example comparing int and long:
This was tested with nitrite 4.3.0 and also shows the same results when comparing int and double.
The text was updated successfully, but these errors were encountered: