Database

Applies to ✅ Open Source Edition   ✅ Express Edition   ✅ Professional Edition   ✅ Enterprise Edition

This element wraps all the configuration elements that are used for the jooq-meta module, which reads the configured database meta data. In its simplest form, it can be left empty, when meaningful defaults will apply.

The two main elements in the <database/> element are <name/> and <properties>, which specify the class to implement the database meta data source, and an optional list of key/value parameters, which are described in the next chapter

Subsequent elements are:

Table of contents

5.2.5.1.

Database name and properties

5.2.5.2.

Inline database implementation (new)

5.2.5.3.

RegexFlags

5.2.5.4.

Includes and Excludes

5.2.5.5.

Include object types

5.2.5.6.

Record Version and Timestamp Fields

5.2.5.7.

Comments

5.2.5.8.

Synthetic objects

5.2.5.8.1.

Synthetic columns

5.2.5.8.2.

Synthetic readonly columns

5.2.5.8.3.

Synthetic readonly ROWIDs

5.2.5.8.4.

Synthetic identities

5.2.5.8.5.

Synthetic enums (new)

5.2.5.8.6.

Synthetic primary keys

5.2.5.8.7.

Synthetic unique keys

5.2.5.8.8.

Synthetic foreign keys

5.2.5.9.

Date as timestamp

5.2.5.10.

Ignore procedure return values (deprecated)

5.2.5.11.

Readonly columns

5.2.5.12.

Unsigned types

5.2.5.13.

Catalog and schema mapping

5.2.5.14.

Catalog and schema version providers

5.2.5.15.

Custom ordering of generated code

5.2.5.16.

Forced types

5.2.5.16.1.

Matching of forced types

5.2.5.16.2.

Data type rewriting

5.2.5.16.3.

Qualified converters

5.2.5.16.4.

Inline converters

5.2.5.16.5.

Lambda converters

5.2.5.16.6.

Auto converters

5.2.5.16.7.

Enum converters

5.2.5.16.8.

Jackson converters

5.2.5.16.9.

JAXB converters

5.2.5.16.10.

Data type bindings

5.2.5.16.11.

Client side computed columns

5.2.5.16.12.

Audit columns

5.2.5.16.13.

Visibility Modifier (per forced type)

5.2.5.17.

Table valued functions