Search icon CANCEL
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Conferences
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
jOOQ Masterclass

You're reading from   jOOQ Masterclass A practical guide for Java developers to write SQL queries for complex database interactions

Arrow left icon
Product type Paperback
Published in Aug 2022
Publisher Packt
ISBN-13 9781800566897
Length 764 pages
Edition 1st Edition
Languages
Tools
Arrow right icon
Author (1):
Arrow left icon
Anghel Leonard Anghel Leonard
Author Profile Icon Anghel Leonard
Anghel Leonard
Arrow right icon
View More author details
Toc

Table of Contents (26) Chapters Close

Preface 1. Part 1: jOOQ as a Query Builder, SQL Executor, and Code Generator
2. Chapter 1: Starting jOOQ and Spring Boot FREE CHAPTER 3. Chapter 2: Customizing the jOOQ Level of Involvement 4. Part 2: jOOQ and Queries
5. Chapter 3: jOOQ Core Concepts 6. Chapter 4: Building a DAO Layer (Evolving the Generated DAO Layer) 7. Chapter 5: Tackling Different Kinds of SELECT, INSERT, UPDATE, DELETE, and MERGE 8. Chapter 6: Tackling Different Kinds of JOINs 9. Chapter 7: Types, Converters, and Bindings 10. Chapter 8: Fetching and Mapping 11. Part 3: jOOQ and More Queries
12. Chapter 9: CRUD, Transactions, and Locking 13. Chapter 10: Exporting, Batching, Bulking, and Loading 14. Chapter 11: jOOQ Keys 15. Chapter 12: Pagination and Dynamic Queries 16. Part 4: jOOQ and Advanced SQL
17. Chapter 13: Exploiting SQL Functions 18. Chapter 14: Derived Tables, CTEs, and Views 19. Chapter 15: Calling and Creating Stored Functions and Procedures 20. Chapter 16: Tackling Aliases and SQL Templating 21. Chapter 17: Multitenancy in jOOQ 22. Part 5: Fine-tuning jOOQ, Logging, and Testing
23. Chapter 18: jOOQ SPI (Providers and Listeners) 24. Chapter 19: Logging and Testing 25. Other Books You May Enjoy

Expressing SQL aliases in jOOQ

SQL aliasing is a simple task. After all, it's just about giving some nicknames to your columns and tables and referring to them via these nicknames instead of using their real names. But as simple as this may seem, this is a rather controversial topic. Some of the open questions you may come across will sound like this: Should I only use aliases when it's mandatory (for instance, when I reference the same table twice)? Should I use meaningful names or will single letters work just fine (p, q, t1, t2, and so on)? Do they increase readability and decrease typing time? Most probably, the correct answer is that it depends… on the context, on the query, on who is writing the query (a developer, a DBA, a generator), and so on!

As you'll see shortly, using aliasing via a DSL requires us to respect several rules and to be prepared for some verbosity since the host language (here, Java) comes with several shortcomings that a DSL must...

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at €18.99/month. Cancel anytime