Natively supported values are:

• {@link org.jooq.meta.ase.ASEDatabase}
• {@link org.jooq.meta.cubrid.CUBRIDDatabase}
• {@link org.jooq.meta.db2.DB2Database}
• {@link org.jooq.meta.derby.DerbyDatabase}
• {@link org.jooq.meta.firebird.FirebirdDatabase}
• {@link org.jooq.meta.h2.H2Database}
• {@link org.jooq.meta.hana.HanaDatabase}
• {@link org.jooq.meta.hsqldb.HSQLDBDatabase}
• {@link org.jooq.meta.informix.InformixDatabase}
• {@link org.jooq.meta.ingres.IngresDatabase}
• {@link org.jooq.meta.mariadb.MariaDBDatabase}
• {@link org.jooq.meta.mysql.MySQLDatabase}
• {@link org.jooq.meta.oracle.OracleDatabase}
• {@link org.jooq.meta.postgres.PostgresDatabase}
• {@link org.jooq.meta.redshift.RedshiftDatabase}
• {@link org.jooq.meta.sqlite.SQLiteDatabase}
• {@link org.jooq.meta.sqlserver.SQLServerDatabase}
• {@link org.jooq.meta.sybase.SybaseDatabase}
• {@link org.jooq.meta.vertica.VerticaDatabase}

This value can be used to reverse-engineer generic JDBC DatabaseMetaData (e.g. for MS Access).

• {@link org.jooq.meta.jdbc.JDBCDatabase}

This value can be used to reverse-engineer standard jOOQ-meta XML formats.

• {@link org.jooq.meta.xml.XMLDatabase}

This value can be used to reverse-engineer JPA annotated entities

• {@link org.jooq.meta.extensions.jpa.JPADatabase}

You can also provide your own org.jooq.meta.Database implementation here, if your database is currently not supported]]> Known supported properties include:

• {@link org.jooq.meta.xml.XMLDatabase}

  dialect=ORACLE
  xml-file=C:\path\to\database.xml
  xsl-files=C:\path\to\1.xsl,C:\path\to\2.xsl

• {@link org.jooq.meta.extensions.jpa.JPADatabase}

  packages=com.example.entities

• {@link org.jooq.meta.extensions.ddl.DDLDatabase}

  scripts=C:\path\to\database.sql
  encoding=UTF-8

You can create case-insensitive regular expressions using this syntax: (?i:expr)

Whitespace is ignored and comments are possible unless overridden in {@link #getRegexFlags()}.]]> This is a Java regular expression. Use the pipe to separate several expressions. Excludes match before includes, i.e. excludes have a higher priority.]]> This is a Java regular expression. Use the pipe to separate several expressions. See {@link org.jooq.UpdatableRecord.store()} and {@link org.jooq.UpdatableRecord.delete()} for details about optimistic locking.]]> This is a Java regular expression. Use the pipe to separate several expressions. See {@link org.jooq.UpdatableRecord.store()} and {@link org.jooq.UpdatableRecord.delete()} for details about optimistic locking.]]> To be used if columns are not detected as automatically as identities.]]> To be used with:

• {@link org.jooq.UpdatableRecord.store()}
• {@link org.jooq.UpdatableRecord.update()}
• {@link org.jooq.UpdatableRecord.delete()}
• {@link org.jooq.UpdatableRecord.refresh()}

Synthetic primary keys will override existing primary keys.]]> To be used with:

• {@link org.jooq.UpdatableRecord.store()}
• {@link org.jooq.UpdatableRecord.update()}
• {@link org.jooq.UpdatableRecord.delete()}
• {@link org.jooq.UpdatableRecord.refresh()}

If several keys match, a warning is emitted and the first one encountered will be used.

This flag will also replace synthetic primary keys, if it matches.]]> In jOOQ 3.6.0, #4106 was implemented to support Transact-SQL's optional return values from stored procedures. This turns all procedures into Routine (instead of Routine). For backwards- compatibility reasons, users can suppress this change in jOOQ 3.x

@deprecated This feature is deprecated as of jOOQ 3.6.0 and will be removed again in jOOQ 4.0.]]> This cannot be combined with the {@link #getCatalogs()} configuration element. If left empty (and without any {@link #getCatalogs()} configuration element), jOOQ will generate all available catalogs.]]> Use this to override your local development catalog name for source code generation. If not specified, this will be the same as {@link #getInputCatalog()}

This will be ignored if {@link #isOutputCatalogToDefault()} is set to true]]> This cannot be combined with the {@link #getSchemata()} configuration element. If left empty (and without any {@link #getSchemata()} configuration element), jOOQ will generate all available schemata.]]> Use this to override your local development schema name for source code generation. If not specified, this will be the same as {@link #getInputSchema()}. This will be ignored if {@link #isOutputSchemaToDefault()} is set to true]]> This configuration element cannot be used at the same time as the {@link #getSchemata()} configuration element.]]> Using this configuration element in an enviroment that supports multiple catalogs means that all catalogs are generated.

This configuration element cannot be used at the same time as the {@link #getCatalogs()} configuration element.]]> There are three operation modes for this element:

• The value is a class that can be found on the classpath and that implements {@link org.jooq.meta.SchemaVersionProvider}. Such classes must provide a default constructor
• The value is a SELECT statement that returns one record with one column. The SELECT statement may contain a named variable called :schema_name
• The value is a constant, such as a Maven property

Schema versions will be generated into the {@link javax.annotation.Generated} annotation on generated artefacts.]]> There are three operation modes for this element:

• The value is a class that can be found on the classpath and that implements {@link org.jooq.meta.CatalogVersionProvider}. Such classes must provide a default constructor
• The value is a SELECT statement that returns one record with one column. The SELECT statement may contain a named variable called :catalog_name
• The value is a constant, such as a Maven property

Catalog versions will be generated into the {@link javax.annotation.Generated} annotation on generated artefacts.]]> This comparator can be used to influence the order of any object that is produced by jOOQ meta, and thus, indirectly, the order of declared objects in generated code.]]> If this is deactivated, such functions are not generated as tables, but as ordinary routines. This is particularly useful for backwards- compatibility between jOOQ 3.8 and previous versions, when using TABLE and VARRAY types in Oracle.

While this flag defaults to true for most databases, it defaults to false for Oracle.]]> If provided, {@link #getName()} will be ignored, and either {@link #getConverter()} or {@link #getBinding()} is required]]> If this flag is set to false, then:

• Column name : X_INDEX
• Attribute name: xIndex
• Getter name : getXIndex()
• Setter name : setXIndex()

If this flag is set to true, then:

• Getter name : getxIndex()
• Setter name : setxIndex()

Custom GeneratorStrategy implementations are unaffected]]> This may lead to compilation warnings in current Java versions.]]> This can be useful if you have a database object that generates a String class, and you want to avoid naming clashes with the java.lang package by specifying java\.lang\..*]]> configurations) should still be generated.]]> configurations) should still be generated.]]> This flag is ignored in the commercial Java 6 distribution of jOOQ 3.9+ ]]> jOOQ may append the schema name to this package if generating multiple schemas, e.g. org.jooq.generated.schema1, org.jooq.generated.schema2]]>