Available in versions: Dev (3.20) | Latest (3.19) | 3.18 | 3.17 | 3.16 | 3.15 | 3.14 | 3.13 | 3.12 | 3.11 | 3.10
This documentation is for the unreleased development version of jOOQ. Click on the above version links to get this documentation for a supported version of jOOQ.
Forced types
Applies to ✅ Open Source Edition ✅ Express Edition ✅ Professional Edition ✅ Enterprise Edition
The code generator allows users to override column, attribute, and parameter data types, as well as other attributes in three different ways:
- By rewriting them to some other data type using the data type rewriting feature.
- By mapping them to some user type using the data type converter feature and a custom
org.jooq.Converter. - By mapping them to some user type using the data type binding feature and a custom
org.jooq.Binding.
All of this, and more, can be done using forced types.
Table of contents
- 5.2.5.17.1.
- Matching of forced types
- 5.2.5.17.2.
- Data type rewriting
- 5.2.5.17.3.
- Qualified converters
- 5.2.5.17.4.
- Inline converters
- 5.2.5.17.5.
- Lambda converters
- 5.2.5.17.6.
- Auto converters
- 5.2.5.17.7.
- Enum converters
- 5.2.5.17.8.
- Jackson converters
- 5.2.5.17.9.
- JAXB converters
- 5.2.5.17.10.
- Data type bindings
- 5.2.5.17.11.
- Client side computed columns
- 5.2.5.17.12.
- Audit columns
- 5.2.5.17.13.
- Hidden columns (new)
- 5.2.5.17.14.
- Visibility Modifier (per forced type)
| previous : next |
Feedback
Do you have any feedback about this page? We'd love to hear it!