Reinvented constructor expressions
Take a look at the following code:
The above Querydsl construction means: create new JPQL query [1] [2], using employee as the data source, order the data using employee name [3], and return the list of EmployeeNameProjection, built using the 2-arg constructor called with employee ID and name [4]. This is very similar to the constructor expressions example from my previous post (JPA - Basic Projections), and leads to the following SQL query:
select EMPLOYEE_ID, EMPLOYEE_NAME from EMPLOYEE order by EMPLOYEE_NAME asc
As you see above, the main advantage comparing to the JPA constructor expressions is using Java class, instead of its name hard-coded in JPQL query.
Querydsl documentation [4] describes another way of using constructor expressions, requiring @QueryProjection annotation and Query Type [1] usage for projection, see example below. Let's start with the projection class modification - note that I added @QueryProjection annotation on the class constructor.
Now we may use modified projection class (and corresponding Query Type [1] ) in following way:
Which leads to SQL query:
Even more reinvented constructor expressions
Querydsl documentation [4] describes another way of using constructor expressions, requiring @QueryProjection annotation and Query Type [1] usage for projection, see example below. Let's start with the projection class modification - note that I added @QueryProjection annotation on the class constructor.
Now we may use modified projection class (and corresponding Query Type [1] ) in following way:
Which leads to SQL query:
select EMPLOYEE_ID, EMPLOYEE_NAME from EMPLOYEE order by EMPLOYEE_NAME asc
In fact, when you take a closer look at the Query Type [1] generated for EmployeeNameProjection (QEmployeeNameProjection), you will see it is some kind of "shortcut" for creating constructor expression the way described in first section of this post.
Mapping projection
Querydsl provides another way of building projections, using factories based on MappingProjection.
The above class is a simple factory creating EmployeeNameProjection instances using employee ID and name. Note that the factory constructor defines which employee properties will be used for building the projection, and map method defines how the instances will be created.
Below you may find an example of using the factory:
As you see, the one and only difference here, comparing to constructor expression examples, is the list method call.
Above example leads again to the very simple SQL query:
Below you may find an example of using the factory:
As you see, the one and only difference here, comparing to constructor expression examples, is the list method call.
Above example leads again to the very simple SQL query:
select EMPLOYEE_ID, EMPLOYEE_NAME from EMPLOYEE order by EMPLOYEE_NAME asc
Building projections this way is much more powerful, and doesn't require existence of n-arg projection constructor.
QBean based projection (JavaBeans strike again)
There is at least one more possibility of creating projection with Querydsl - QBean based - in this case we build the result list using:
... .list(Projections.bean(EmployeeNameProjection.class, employee.employeeId, employee.name))
This way requires EmployeeNameProjection class to follow JavaBean conventions, which is not always desired in application. Use it if you want, but you have been warned ;)
Few links for the dessert
Follow-ups:
This article has been republished on Java Code Geeks (05/14/2013), and on Dzone's Javalobby (05/15/2013).
No comments:
Post a Comment