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

JPA: limit requires a long yet casts it into an int #392

Closed
ponzao opened this issue Apr 10, 2013 · 2 comments
Closed

JPA: limit requires a long yet casts it into an int #392

ponzao opened this issue Apr 10, 2013 · 2 comments
Labels
Milestone

Comments

@ponzao
Copy link
Contributor

@ponzao ponzao commented Apr 10, 2013

I am using Long.MAX_VALUE which ends up as a negative value when it is cast into an int inside Querydsl.

As a fix if the boundary as is exceeded perhaps use Integer.MAX_VALUE?

@timowest
Copy link
Member

@timowest timowest commented Apr 10, 2013

Thanks for the bug report. Limit/offset usage should now be safe for int conversions.

@timowest
Copy link
Member

@timowest timowest commented Apr 16, 2013

Released in 3.1.1

@timowest timowest closed this Apr 16, 2013
@timowest timowest added this to the 3.1.1 milestone Apr 14, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants