| The jOOQ User Manual. Multiple Pages : SQL building : The DSLContext API : Custom Settings : Object qualification | previous : next |
All versions: 3.13 | 3.12 | 3.11 | 3.10 | 3.9 | 3.8 | Development versions: 3.14 | Unsupported versions: 3.7 | 3.6 | 3.5 | 3.4 | 3.3
Object qualification
Available in ✅ Open Source Edition ✅ Express Edition ✅ Professional Edition ✅ Enterprise Edition
By default, jOOQ fully qualifies all objects with their catalog and schema names, if such qualification is made available by the code generator. For instance, the following SQL statement containing full qualification may be produced by jOOQ code with seemingly no qualification:
-- Full qualification on columns and tables SELECT catalog.schema.table.column FROM catalog.schema.table
DSL.using(configuration) .select(TABLE.COLUMN) // Column only qualified with table .from(TABLE) // No qualification on table
While the jOOQ code is also implicitly fully qualified (see implied imports), it may not be desireable to use fully qualified object names in SQL. The renderCatalog and renderSchema settings are used for this.
Programmatic configuration
new Settings() .withRenderCatalog(false) // Defaults to true .withRenderSchema(false) // Defaults to true
XML configuration
<settings xmlns="http://www.jooq.org/xsd/jooq-runtime-3.8.0.xsd"> <renderCatalog>false</renderCatalog> <renderSchema>false</renderSchema> </settings>
By turning off the rendering of full qualification as can be seen above, it will be possible to use code generated from one schema on an entirely different schema of the same structure, e.g. for multitenancy purposes.
More sophisticated multitenancy approaches are available through the render mapping feature.
