View on GitHub

QLRM

Query Language Result Mapper

Download this project as a .zip file Download this project as a tar.gz file

Why?

In JPA there is no Constructor Expression for native SQL queries. QLRM fills the gap!

And because the implementation was quite easy there is an implementation for JDBC resultsets as well.

But what about JPA 2.1 and the ConstructorResult?

Read more: https://github.com/simasch/qlrm/blob/master/ConstructorResult.md

Maven Dependency

QLRM is available in Maven Central

<dependency>
    <groupId>ch.simas.qlrm</groupId>
    <artifactId>qlrm</artifactId>
    <version>1.6.9</version>
</dependency>

NEW in 1.7.0: QueryExecutors

Sometimes it's cleaner to move the SQL statements to a file but how to execute these statements?

QueryExecutors to the rescue!

There is an implemenation that takes a JDBC connection and one using the JPA EntityManager.

JDBC

JdbcQueryExecutor queryExecutor = new JdbcQueryExecutor();
List<EmployeeTO> list = queryExecutor.executeSelect(con, EmployeeTO.class, "select_with_one_param.sql", 1);

JPA

JpaQueryExecutor queryExecutor = new JpaQueryExecutor();
List<EmployeeTO> list = queryExecutor.executeSelect(em, EmployeeTO.class, "select_with_one_param.sql", 1);

ResultMapper

The usage is quite forward but be aware of:

JPA Native Query

List

JpaResultMapper jpaResultMapper = new JpaResultMapper();

Query q = em.createNativeQuery("SELECT ID, NAME FROM EMPLOYEE");
List<EmployeeTO> list = jpaResultMapper.list(q, EmployeeTO.class);

Unique Result

Query q = em.createNativeQuery("SELECT ID, NAME FROM EMPLOYEE WHERE ID = 1");
EmployeeTO to = jpaResultMapper.uniqueResult(q, EmployeeTO.class);

JPQL

List

Query q = em.createQuery("SELECT e.id, e.name FROM Employee e");
List<EmployeeTO> list = jpaResultMapper.list(q, EmployeeTO.class);

Unique Result

Query q = em.createNativeQuery("SELECT e.id, e.name FROM Employee e WHERE e.id = 1");
EmployeeTO to = jpaResultMapper.uniqueResult(q, EmployeeTO.class);

JDBC SQL

List

JdbcResultMapper jdbcResultMapper = new JdbcResultMapper();

stmt.execute("SELECT ID, NAME FROM EMPLOYEE");
List<EmployeeTO> list = jdbcResultMapper.list(stmt.getResultSet(), EmployeeTO.class);

Unique Result

boolean ok = stmt.execute("SELECT ID, NAME FROM EMPLOYEE WHERE ID = 1");
EmployeeTO to = jdbcResultMapper.uniqueResult(stmt.getResultSet(), EmployeeTO.class);

References

The QL Result Mapper is inspired by EclipseLink and Hibernate:

Class Generator

ClassGenerator is a simple utility to generate transfer objects from database tables.

Usage

The first parameter is the path where the source file should be generated to. The second is the package name, third a suffix. With the forth parameter you can define if the fields should be public or if the generator must generate getters. Then a database connection must be passed. And the last parameter is a vargargs where you can passe one or multiple table names.

ClassGenerator classGenerator = new ClassGenerator();

classGenerator.generateFromTables("src/test/java/", "ch.simas.sqlresultmapper.to", "TO", false, con, "EMPLOYEE");

Release Notes

QLRM 1.7.0

QLRM 1.6.9

QLRM 1.6.8

QLRM 1.6.6

QLRM 1.6.4

QLRM 1.6.3 Bugfix

QLRM 1.6.1 New Features

Contributors

Special thanks for their contribution to

License

SQL Result Mapper is open source and free software under Apache License, Version 2:

http://www.apache.org/licenses/LICENSE-2.0.html