Available in versions: Dev (3.21) | Latest (3.20) | 3.19 | 3.18 | 3.17 | 3.16 | 3.15 | 3.14 | 3.13 | 3.12 | 3.11
Class names, method names, identifiers
Applies to ✅ Open Source Edition ✅ Express Edition ✅ Professional Edition ✅ Enterprise Edition
By default, generated class names, method names, identifiers, etc. follow Java's typical naming conventions.
Assuming a table like this:
CREATE TABLE account_transactions ( id INTEGER NOT NULL, created_at TIMESTAMP NOT NULL, created_by VARCHAR(100) NOT NULL, ... );
As a rule of thumb, the following defaults can be assumed for named objects:
- Class names follow
PascalCasenaming, i.e. theorg.jooq.Tableclass name isAccountTransactions - Records have a
Recordsuffix, i.e. theorg.jooq.UpdatableRecordclass name isAccountTransactionsRecord - Daos have a
Daosuffix, i.e. theorg.jooq.DAOclass name isAccountTransactionsDao - Identifiers follow
SNAKE_CASEnaming, i.e. theorg.jooq.Tableinstance name isACCOUNT_TRANSACTIONS - Path methods follow a
camleCasenaming, i.e. theorg.jooq.Pathmethod name isaccountTransactions()(e.g. on a child table)
If these defaults do not convene, or if a workaround needs to be applied for a limitation of the default naming, generator strategies allow for overriding these defaults.
Table of contents
- 5.5.1.
- Custom generator strategies
- 5.5.2.
- Matcher strategies
- 5.5.2.1.
- MatcherRule
- 5.5.2.2.
- Matching catalogs
- 5.5.2.3.
- Matching schemas
- 5.5.2.4.
- Matching tables
- 5.5.2.5.
- Matching fields
- 5.5.2.6.
- Matching indexes
- 5.5.2.7.
- Matching primary keys
- 5.5.2.8.
- Matching unique keys
- 5.5.2.9.
- Matching foreign keys
- 5.5.2.10.
- Matching routines
- 5.5.2.11.
- Matching sequences
- 5.5.2.12.
- Matching enums
- 5.5.2.13.
- Matching embeddables
- 5.5.2.14.
- Matching UDTs
- 5.5.2.15.
- Matching attributes
- 5.5.2.16.
- Matcher examples
| previous : next |
Feedback
Do you have any feedback about this page? We'd love to hear it!