We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
We observe the following behaviour starting with spring-data-jpa 3.3.9. (3.3.8 was fine)
With a JPA query like this
@Query(""" SELECT p.id FROM Parent p WHERE (:ids is null OR p.id IN (:ids)) """) Page<Long> withIds(@Param("ids")List<Long> ids, Pageable pageable);
if the result size is bigger than the Pageable page size it throws
org.springframework.dao.InvalidDataAccessResourceUsageException: No argument for named parameter ':ids_1'
if the result size is smaller than the Pageable page size it behaves like expected.
see this branch to reproduce https://github.com/spring-projects/spring-data-jpa/compare/3.3.9...aperreaultaubeupgrade:spring-data-jpa:jpa-is-null-pageable-bug?expand=1
The text was updated successfully, but these errors were encountered:
Thank you for getting in touch - seems you're hitting a regression reported via #3784.
Sorry, something went wrong.
No branches or pull requests
We observe the following behaviour starting with spring-data-jpa 3.3.9. (3.3.8 was fine)
With a JPA query like this
if the result size is bigger than the Pageable page size it throws
org.springframework.dao.InvalidDataAccessResourceUsageException: No argument for named parameter ':ids_1'
if the result size is smaller than the Pageable page size it behaves like expected.
see this branch to reproduce
https://github.com/spring-projects/spring-data-jpa/compare/3.3.9...aperreaultaubeupgrade:spring-data-jpa:jpa-is-null-pageable-bug?expand=1
The text was updated successfully, but these errors were encountered: