Example Analysis of JPA Native SQL paging query Logic

This article will explain in detail the example analysis of JPA native SQL paging query logic. The editor thinks it is very practical, so I share it with you for reference. I hope you can get something after reading this article.

JPA native SQL (custom SQL) paging query

If JPA writes his own SQL query, paging is still a little troublesome.

After testing, the following method can be @ Query (nativeQuery = true, value = "select * from goods where" + "codeName like CONCAT ('%',? 1 pageable%') and order by? W # {# pageable}") Page findByName (String name, Pageable pageable); the field Pageable pageable = new PageRequest (pageNumber, pageSize,Sort.Direction.DESC, "id") defined in the pageable object; and JPA native SQL paging query trample record 1. A brief description of the problem

JPA paging query this is very simple, as long as add a parameter Pageable to the interface

such as

But take a closer look at my custom SQL where A. * is used to get only one table field.

But the SQL statement he generated became.

This results in an exception to the query.

two。 Solution

1. Specify the fields of the count

Add a parameter to the @ Query annotation

Then, the generated SQL statement is

two。 Specify the query statement for count

Also add parameters to @ Query

This is the end of the article on "sample analysis of JPA native SQL paging query logic". I hope the above content can be helpful to you, so that you can learn more knowledge. if you think the article is good, please share it for more people to see.