Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

predicate on date field #135

psfung opened this issue Apr 26, 2012 · 1 comment


Copy link

@psfung psfung commented Apr 26, 2012

This is not the first time I complain about predicate on date field, the last time was

I don't understand why the value needs to be converted from a String in AbstractPredicate.getRealObject(). The conversion has loss of precision because the date format does not have the millisecond part.

Worse, when the date field is indexed (with order), the hashcode returned from Index.getLongValue() is compared. It's simply wrong.


This comment has been minimized.

Copy link

@mdogan mdogan commented Apr 26, 2012

Value does not need to be converted from a String unless you are using an SqlPredicate.

Yes, indexing of dates is wrong, we can fix this.

@mdogan mdogan closed this in ee5fe0d Apr 27, 2012
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet
2 participants
You can’t perform that action at this time.