The schema, top-level generated artefact

This version of the manual is outdated. For the latest version, follow this link: http://www.jooq.org/doc/3.0/manual.

# The Schema

As of jOOQ 1.5, the top-level generated object is the org.jooq.Schema. The Schema itself has no relevant functionality, except for holding the schema name for all dependent generated artefacts. jOOQ queries try to always fully qualify an entity within the database using that Schema

Currently, it is not possible to link generated artefacts from various schemata. If you have a stored function from Schema A, which returns a UDT from Schema B, the types cannot be linked. This enhancement is on the roadmap, though: #282.

When you have several schemata that are logically equivalent (i.e. they contain identical entities, but the schemata stand for different users/customers/clients, etc), there is a solution for that. Check out the manual's section on support for multiple equivalent schemata

# Schema contents

The schema can be used to dynamically discover generate database artefacts. Tables, sequences, and other items are accessible from the schema. For example:

public final java.util.List<org.jooq.Sequence<?>> getSequences();
public final java.util.List<org.jooq.Table<?>> getTables();