Available in versions: Dev (3.19) | Latest (3.18) | 3.17 | 3.16 | 3.15 | 3.14 | 3.13 | 3.12 | 3.11 | 3.10 | 3.9
Matching tables
Applies to ✅ Open Source Edition ✅ Express Edition ✅ Professional Edition ✅ Enterprise Edition
The following example shows how to define a MatcherStrategy for generated org.jooq.Table and org.jooq.TableRecord types and related objects:
XML (standalone and maven)
Programmatic
Gradle (Kotlin)
Gradle (Groovy)
Gradle (third party)
<configuration>
<!-- These properties can be added directly to the generator element: -->
<generator>
<strategy>
<matchers>
<!-- Specify 0..n table matchers to provide a strategy for naming objects created from tables. -->
<tables>
<table>
<!-- Match unqualified or qualified table names. If left empty, this matcher applies to all tables. -->
<expression>MY_TABLE</expression>
<!-- These elements influence the naming of a generated org.jooq.Table object. -->
<tableClass> a MatcherRule specification </tableClass>
<tableIdentifier> a MatcherRule specification </tableIdentifier>
<tableImplements>com.example.MyOptionalCustomInterface</tableImplements>
<!-- These elements influence the naming of a generated org.jooq.Record object. -->
<recordClass> a MatcherRule specification </recordClass>
<recordImplements>com.example.MyOptionalCustomInterface</recordImplements>
<!-- These elements influence the naming of a generated interface, implemented by
generated org.jooq.Record objects and by generated POJOs. -->
<interfaceClass> a MatcherRule specification </interfaceClass>
<interfaceImplements>com.example.MyOptionalCustomInterface</interfaceImplements>
<!-- These elements influence the naming of a generated org.jooq.DAO object. -->
<daoClass> a MatcherRule specification </daoClass>
<daoImplements>com.example.MyOptionalCustomInterface</daoImplements>
<!-- These elements influence the naming of a generated POJO object. -->
<pojoClass> a MatcherRule specification </pojoClass>
<pojoExtends>com.example.MyOptionalPojoBaseClass</pojoExtends>
<pojoImplements>com.example.MyOptionalCustomInterface</pojoImplements>
</table>
</tables>
</matchers>
</strategy>
</generator>
</configuration>
See the configuration XSD, standalone code generation, and maven code generation for more details.
new org.jooq.util.jaxb.Configuration()
// These properties can be added directly to the generator element:
.withGenerator(new Generator()
.withStrategy(new Strategy()
.withMatchers(new Matchers()
// Specify 0..n table matchers to provide a strategy for naming objects created from tables.
.withTables(
new MatchersTableType()
// Match unqualified or qualified table names. If left empty, this matcher applies to all tables.
.withExpression("MY_TABLE")
// These elements influence the naming of a generated org.jooq.Table object.
.withTableClass(MatcherRule. a MatcherRule specification )
.withTableIdentifier(MatcherRule. a MatcherRule specification )
.withTableImplements("com.example.MyOptionalCustomInterface")
// These elements influence the naming of a generated org.jooq.Record object.
.withRecordClass(MatcherRule. a MatcherRule specification )
.withRecordImplements("com.example.MyOptionalCustomInterface")
// These elements influence the naming of a generated interface, implemented by
// generated org.jooq.Record objects and by generated POJOs.
.withInterfaceClass(MatcherRule. a MatcherRule specification )
.withInterfaceImplements("com.example.MyOptionalCustomInterface")
// These elements influence the naming of a generated org.jooq.DAO object.
.withDaoClass(MatcherRule. a MatcherRule specification )
.withDaoImplements("com.example.MyOptionalCustomInterface")
// These elements influence the naming of a generated POJO object.
.withPojoClass(MatcherRule. a MatcherRule specification )
.withPojoExtends("com.example.MyOptionalPojoBaseClass")
.withPojoImplements("com.example.MyOptionalCustomInterface")
)
)
)
)
See the configuration XSD and programmatic code generation for more details.
// The jOOQ-codegen-gradle plugin has been introduced in version 3.19 only.
// The jOOQ-codegen-gradle plugin has been introduced in version 3.19 only.
generationTool {
// These properties can be added directly to the generator element:
generator {
strategy {
matchers {
// Specify 0..n table matchers to provide a strategy for naming objects created from tables.
tables {
table {
// Match unqualified or qualified table names. If left empty, this matcher applies to all tables.
expression = "MY_TABLE"
// These elements influence the naming of a generated org.jooq.Table object.
tableClass = " a MatcherRule specification "
tableIdentifier = " a MatcherRule specification "
tableImplements = "com.example.MyOptionalCustomInterface"
// These elements influence the naming of a generated org.jooq.Record object.
recordClass = " a MatcherRule specification "
recordImplements = "com.example.MyOptionalCustomInterface"
// These elements influence the naming of a generated interface, implemented by
// generated org.jooq.Record objects and by generated POJOs.
interfaceClass = " a MatcherRule specification "
interfaceImplements = "com.example.MyOptionalCustomInterface"
// These elements influence the naming of a generated org.jooq.DAO object.
daoClass = " a MatcherRule specification "
daoImplements = "com.example.MyOptionalCustomInterface"
// These elements influence the naming of a generated POJO object.
pojoClass = " a MatcherRule specification "
pojoExtends = "com.example.MyOptionalPojoBaseClass"
pojoImplements = "com.example.MyOptionalCustomInterface"
}
}
}
}
}
}
See the configuration XSD and gradle code generation for more details.
As always, when regular expressions are used, they are regular expressions with default flags.
See MatcherRule for more information about MatcherRule specifications.
Feedback
Do you have any feedback about this page? We'd love to hear it!