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
Default catalog and schema
Applies to ✅ Open Source Edition ✅ Express Edition ✅ Professional Edition ✅ Enterprise Edition
Generated catalog and schema objects have purposes other than qualifying their contents, such as tables, sequences, routines, etc. Some of these purposes include:
- mapping of qualifiers
- declaring of version providers to prevent unnecessary re-generation
- declaring of qualifier based global artefacts
This is why jOOQ generates a DefaultCatalog and DefaultSchema instance even when there are no catalogs or schemas in the database, or when the catalogs or schemas have been mapped to the default.
If generating these defaults is not a desireable, it can be deactivated explicitly globally using the following flag:
<configuration>
<generator>
<generate>
<defaultCatalog>false</defaultCatalog>
<defaultSchema>false</defaultSchema>
</generate>
</generator>
</configuration>
See the configuration XSD, standalone code generation, and maven code generation for more details.
new org.jooq.meta.jaxb.Configuration()
.withGenerator(
new Generate()
.withDefaultCatalog(false)
.withDefaultSchema(false)
)
See the configuration XSD and programmatic code generation for more details.
import org.jooq.meta.jaxb.*
configuration {
generator {
generate {
isDefaultCatalog = false
isDefaultSchema = false
}
}
}
See the configuration XSD and gradle code generation for more details.
configuration {
generator {
generate {
defaultCatalog = false
defaultSchema = false
}
}
}
See the configuration XSD and gradle code generation for more details.
generationTool {
generator {
generate {
defaultCatalog = false
defaultSchema = false
}
}
}
See the configuration XSD and gradle code generation for more details.
Feedback
Do you have any feedback about this page? We'd love to hear it!