diff --git a/jOOQ-manual/src/main/resources/org/jooq/web/manual-3.11.xml b/jOOQ-manual/src/main/resources/org/jooq/web/manual-3.11.xml index 3d2eeef691..eba907a71e 100644 --- a/jOOQ-manual/src/main/resources/org/jooq/web/manual-3.11.xml +++ b/jOOQ-manual/src/main/resources/org/jooq/web/manual-3.11.xml @@ -4827,6 +4827,117 @@ WHERE NOT EXISTS ( + +
+ Implicit JOIN + +

+ In SQL, a lot of are written simply to retrieve a parent table's column from a given child table. For example, we'll write: +

+ + + +

+ There is quite a bit of syntactic ceremony (or we could even call it "noise") to get a relatively simple job done. A much simpler notation would be using implicit joins: +

+ + +

+ Notice how this alternative notation (depending on your taste) may look more tidy and straightforward, as the semantics of accessing a table's parent table (or an entity's parent entity) is straightforward. +

+ +

+ From jOOQ 3.11 onwards, this syntax is supported for to-one relationship navigation. The code generator produces relevant navigation methods on generated tables, which can be used in a type safe way. The navigation method names are: +

+ + + +

+ This default behaviour can be overridden by using a . +

+ +

+ The jOOQ version of the previous queries looks like this: +

+ + +

+ The generated SQL is almost identical to the original one - there is no performance penalty to this syntax. +

+
+
+
The WHERE clause