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

jOOQ Configuration

org.jooq.Configuration represents the spine of DSLContext. DSLContext needs the precious information provided by Configuration for query rendering and execution. While Configuration takes advantage of Settings (as you just saw), it also has a lot more other configurations that can be specified as in the examples from this section.

By default, Spring Boot gives us a DSLContext built on the default Configuration (the Configuration accessible via ctx.configuration()), and as you know, while providing custom settings and configurations, we can alter this Configuration globally via set() or locally by creating a derived one via derive().

But, in some scenarios, for instance, when you build custom providers or listeners, you'll prefer to build the Configuration to be aware of your artifacts right from the start instead of extracting it from DSLContext. In other words, when DSLContext is built, it should use the ready-to-go Configuration.

Before Spring Boot...