Features requiring generated code

Applies to ✅ Open Source Edition   ✅ Express Edition   ✅ Professional Edition   ✅ Enterprise Edition

There are numerous features in jOOQ that require the use of generated code, which is why we always recommend using generated code by default. The main and only reason why you wouldn't use the code generator is because your schema is dynamic and known only at runtime.

However, even when you use the jOOQ code generator, there are occasions where you may need to bypass it by using plain SQL or Name based Field and Table types. In those cases, you will not benefit from the following features either (the features are effectively bypassed). Such features include:

• INSERT RETURNING, UPDATE RETURNING, and DELETE RETURNING emulations need access to constraint meta data.
• Readonly columns are a code generation feature that is attached to a org.jooq.DataType.
• Computed columns are a code generation feature that is attached to a org.jooq.DataType.
• Audit columns are implemented via computed columns, and thus the same limitations apply.
• Forced types are a code generation feature that is attached to a org.jooq.DataType.
• Policies are a runtime feature, depending on org.jooq.Table equality.
• Render mapping is a runtime feature, depending on org.jooq.Catalog, org.jooq.Schema, or org.jooq.Table equality.
• QueryPart traversal is a runtime feature that depends on a org.jooq.QueryPart being traversable by jOOQ's internals.
• QueryPart replacement is a runtime feature that depends on a org.jooq.QueryPart being traversable by jOOQ's internals.