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

Chapter 11: jOOQ Keys

Choosing the proper type of keys for our tables has a significant benefit on our queries. jOOQ sustains this statement by supporting a wide range of keys, from the well-known unique and primary keys to the fancy embedded and synthetic/surrogate keys. The most commonly used synthetic identifiers (or surrogate identifiers) are numerical or UUIDs. In comparison with natural keys, surrogate identifiers don't have a meaning or a correspondent in the real world. A surrogate identifier can be generated by a Numerical Sequence Generator (for instance, an identity or sequence) or by a Pseudorandom Number Generator (for instance, a GUID or UUID). Moreover, let me use this context to recall that in clustered environments, most relational databases rely on numerical sequences and different offsets per node to avoid the risk of conflicts. Use numerical sequences instead of UUIDs because they require less memory than UUIDs (a UUID requires 16 bytes, while BIGINT requires...