Book Image

jOOQ Masterclass

By : Anghel Leonard
Book Image

jOOQ Masterclass

By: Anghel Leonard

Overview of this book

jOOQ is an excellent query builder framework that allows you to emulate database-specific SQL statements using a fluent, intuitive, and flexible DSL API. jOOQ is fully capable of handling the most complex SQL in more than 30 different database dialects. jOOQ Masterclass covers jOOQ from beginner to expert level using examples (for MySQL, PostgreSQL, SQL Server, and Oracle) that show you how jOOQ is a mature and complete solution for implementing the persistence layer. You’ll learn how to use jOOQ in Spring Boot apps as a replacement for SpringTemplate and Spring Data JPA. Next, you’ll unleash jOOQ type-safe queries and CRUD operations via jOOQ’s records, converters, bindings, types, mappers, multi-tenancy, logging, and testing. Later, the book shows you how to use jOOQ to exploit powerful SQL features such as UDTs, embeddable types, embedded keys, and more. As you progress, you’ll cover trending topics such as identifiers, batching, lazy loading, pagination, and HTTP long conversations. For implementation purposes, the jOOQ examples explained in this book are written in the Spring Boot context for Maven/Gradle against MySQL, Postgres, SQL Server, and Oracle. By the end of this book, you’ll be a jOOQ power user capable of integrating jOOQ in the most modern and sophisticated apps including enterprise apps, microservices, and so on.
Table of Contents (26 chapters)
1
Part 1: jOOQ as a Query Builder, SQL Executor, and Code Generator
4
Part 2: jOOQ and Queries
11
Part 3: jOOQ and More Queries
16
Part 4: jOOQ and Advanced SQL
22
Part 5: Fine-tuning jOOQ, Logging, and Testing

Hooking the DAO layer

DAO is a design pattern that stands for Data Access Object. Following the separation of logic principle, DAO separates the data persistence logic in a dedicated layer and abstracts away the low-level database operations. Typically, the DAO is sketched around three main components:

  • A model representing the data that is transferred between layers (for example, the Sale model corresponds to the SALE database table)
  • An interface containing the API that should be implemented for the model (for example, SaleDao, or in Spring terms, SaleRepository)
  • A concrete implementation of this interface (for example, SaleDaoImpl, or in Spring terms, SaleRepositoryImpl)

The following diagram represents the relationships between these components using Sale, SaleRepository, and SaleRepositoryImpl:

Figure 4.1 – DAO design pattern

If you are a JdbcTemplate fan, you most probably recognize this pattern in your own applications. On...