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
{{ message }}
This repository has been archived by the owner on Nov 23, 2021. It is now read-only.
In our deprecated SearchCriteriaTo, from version 2.x.x, we had a method called limitMaximumPageSize(int limit). I'm trying to replicate it on the new 3.0.0 version. However, as we are now usingPageable, there is no method to limit the maximum hit size.
The way I found to do so is by using PageableDefault, which is an annotation that can be used to limit the maximum hit size like this:
@Query("SELECT foo FROM FooEntity foo"//
+ " WHERE foo.message = :message")
Page<FooEntity> findByMessage(@Param("message") Stringmessage, @PageableDefault(value = MAXIMUM_HIT_LIMIT) Pageablepageable);
I would like this option to be added to the QueryUtil file from OASP4J jpa basic, something similar to this:
In our deprecated SearchCriteriaTo, from version 2.x.x, we had a method called
limitMaximumPageSize(int limit)
. I'm trying to replicate it on the new 3.0.0 version. However, as we are now usingPageable
, there is no method to limit the maximum hit size.The way I found to do so is by using PageableDefault, which is an annotation that can be used to limit the maximum hit size like this:
I would like this option to be added to the QueryUtil file from OASP4J jpa basic, something similar to this:
Perhaps you can tell me another way to do it that I'm not aware of. (Or maybe completely forget about this because it is not important??)
The text was updated successfully, but these errors were encountered: