Don't do this

Supported by ✅ Open Source Edition   ✅ Express Edition   ✅ Professional Edition   ✅ Enterprise Edition

Like any software, jOOQ has a few pitfalls, known issues, historic design flaws, etc., which the seasoned jOOQ developer should know to avoid. This section summarises both of jOOQ's and SQL's own pitfalls.

Table of contents

7.8.1.

jOOQ: Implementing the DSL types

7.8.2.

jOOQ: Referencing the Step types

7.8.3.

Schema: NULL columns

7.8.4.

Schema: Unnamed constraints

7.8.5.

Schema: Unnecessary surrogate keys

7.8.6.

Schema: Wrong data types

7.8.7.

SQL: COUNT(*) instead of EXISTS()

7.8.8.

SQL: N+1

7.8.9.

SQL: NATURAL JOIN or JOIN USING

7.8.10.

SQL: NOT IN predicate

7.8.11.

SQL: ORDER BY [column index]

7.8.12.

SQL: Rely on implicit ordering

7.8.13.

SQL: SELECT *

7.8.14.

SQL: SELECT DISTINCT

7.8.15.

SQL: Unnecessary UNION instead of UNION ALL