NativeQuery with Pagination

[Johnczek]

Hello, I am facing issue similiar with #1282.

I am trying to run this native query with spring-data on version 2.5.0

@Query(value = "SELECT dense_rank() OVER (ORDER BY rank DESC)," + "t.id, " + "FROM table t WHERE t.x > 0 ", nativeQuery = true) Page<Object[]> getT(Pageable pageable);

But I am getting SQLGrammarException because the spring-data engine will translate this query into

SELECT dense_rank() OVER (ORDER BY rank DESC),t.id FROM table t WHERE t.x > 0 , t.y desc limit 20

Where the problem is pretty obvious. There is ORDER BY clause missing, probably because of presence of ORDER BY clause in OVER subquery. Is this a known bug? And is it possible to bypass this somehow? I need to use whole pageable object with native query with this dense_rank() calling.

[schauder]

I suspect this is a bug in the underlying JPA implementation. Spring Data JPA uses Query.setFirstResult and Query.setMaxResult to create the queries for pagination.

Could you confirm that you seeing this behaviour as well if you use an EntityManager directly, as described in https://www.baeldung.com/jpa-pagination

[Johnczek]

I suspect this is a bug in the underlying JPA implementation. Spring Data JPA uses Query.setFirstResult and Query.setMaxResult to create the queries for pagination.

Could you confirm that you seeing this behaviour as well if you use an EntityManager directly, as described in https://www.baeldung.com/jpa-pagination

Hello, I´ve tried many ways but entity manager did not worked for me cause native query has no option to pass sort into query.

But after some investigation I´ve found a workaround with adding ORDER 1 at the end of query and now It is working fine.
I assume that spring will look for ORDER BY substring and if its found, there is (from his point of view) no need to add another ORDER BY and therefore spring appends just , ordering limiting offsetting. But in this case the ORDER BY clause should be added because the found ORDER BY property is not the one that framework is looking for.

[TAndronicus]

I'll try to tackle this issue

[TAndronicus]

I have added a solution where I'm counting the number of occurrences of order by and order by used in window functions. If the former count is greater than the latter, I'm assuming the order by is already present.
Although this fixes the reported issue, I can think of an example where it won't work - when order by is used in nested query (as in @shu1997 comment). Any suggestions are welcome.
Maybe it would be better to exclude all order by matches surrounded by parentheses - this would solve all the issues provided the entire query is not surrounded with parentheses.