TRACE log level.]]> DEBUG log level.]]> INFO log level.]]> WARN log level.]]> ERROR log level.]]> FATAL log level.]]> @java.lang.Deprecated @java.lang.Deprecated JPADatabase, XMLDatabase, or DDLDatabase, or to pass to JDBC drivers.]]> jOOQ internals make a few assumptions about what a {@link org.jooq.Catalog} does, so to minimise unexpected behaviour, custom catalog super classes should extend {@link org.jooq.impl.CatalogImpl} and follow its (undocumented!) assumptions (e.g. constructors, etc.). Use this at your own risk.]]> jOOQ internals make a few assumptions about what a {@link org.jooq.Schema} does, so to minimise unexpected behaviour, custom schema super classes should extend {@link org.jooq.impl.SchemaImpl} and follow its (undocumented!) assumptions (e.g. constructors, etc.). Use this at your own risk.]]> jOOQ internals make a few assumptions about what a {@link org.jooq.Table} does, so to minimise unexpected behaviour, custom table super classes should extend {@link org.jooq.impl.TableImpl} and follow its (undocumented!) assumptions (e.g. constructors, etc.). Use this at your own risk.]]> jOOQ internals make a few assumptions about what a {@link org.jooq.TableRecord} does, so to minimise unexpected behaviour, custom table record super classes should extend {@link org.jooq.impl.TableRecordImpl} and follow its (undocumented!) assumptions (e.g. constructors, etc.). Use this at your own risk.]]> jOOQ internals make a few assumptions about what a {@link org.jooq.DAO} does, so to minimise unexpected behaviour, custom DAO super classes should extend {@link org.jooq.impl.DAOImpl} and follow its (undocumented!) assumptions (e.g. constructors, etc.). Use this at your own risk.]]> jOOQ internals make a few assumptions about what a {@link org.jooq.Routine} does, so to minimise unexpected behaviour, custom routine super classes should extend {@link org.jooq.impl.AbstractRoutine} and follow its (undocumented!) assumptions (e.g. constructors, etc.). Use this at your own risk.]]> jOOQ internals make a few assumptions about what a {@link org.jooq.EmbeddableRecord} does, so to minimise unexpected behaviour, custom embeddable record super classes should extend {@link org.jooq.impl.EmbeddableRecordImpl} and follow its (undocumented!) assumptions (e.g. constructors, etc.). Use this at your own risk.]]> jOOQ internals make a few assumptions about what a {@link org.jooq.UDT} does, so to minimise unexpected behaviour, custom table super classes should extend {@link org.jooq.impl.UDTImpl} and follow its (undocumented!) assumptions (e.g. constructors, etc.). Use this at your own risk.]]> jOOQ internals make a few assumptions about what a {@link org.jooq.UDTRecord} does, so to minimise unexpected behaviour, custom UDT record super classes should extend {@link org.jooq.impl.UDTPathTableFieldImpl} and follow its (undocumented!) assumptions (e.g. constructors, etc.). Use this at your own risk.]]> jOOQ internals make a few assumptions about what a {@link org.jooq.UDTRecord} does, so to minimise unexpected behaviour, custom UDT record super classes should extend {@link org.jooq.impl.UDTRecordImpl} and follow its (undocumented!) assumptions (e.g. constructors, etc.). Use this at your own risk.]]> org.util.[database].[database]Database.

Natively supported values are:

{@link org.jooq.meta.ase.ASEDatabase}
{@link org.jooq.meta.cockroachdb.CockroachDBDatabase}
{@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}
{@link org.jooq.meta.yugabytedb.YugabyteDBDatabase}

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
```

]]> The default value is "COMMENTS CASE_INSENSITIVE"]]> This is a Java regular expression. Use the pipe to separate several expressions. Watch out for case-sensitivity. Depending on your database, this might be important!

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 query that produces Java regular expressions, which are appended to the ones produced by includes. Watch out for case-sensitivity. Depending on your database, this might be important!

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

Whitespace is ignored and comments are possible unless overridden in {@link #getRegexFlags()}.

Excludes match before includes, i.e. excludes have a higher priority.]]> 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 query that produces Java regular expressions, which are appended to the ones produced by excludes. Watch out for case-sensitivity. Depending on your database, this might be important!

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

Whitespace is ignored and comments are possible unless overridden in {@link #getRegexFlags()}.

Excludes match before includes, i.e. excludes have a higher priority.]]> This feature is available in the commercial distribution only.]]> This feature is available in the commercial distribution only.]]> This feature is available in the commercial distribution only.]]> 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.]]> This feature is available in the commercial distribution only.]]> To be used if columns are not detected as automatically as identities.

This will always produce GENERATED BY DEFAULT generation mode. To produce the GENERATED ALWAYS mode, use the more explicit synthetic identity configuration.]]> 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.]]> @java.lang.Deprecated @java.lang.Deprecated 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.processing.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.processing.Generated} annotation on generated artefacts.]]> catalogVersionProvider or schemaVersionProvider allows for skipping regeneration of schemas that are up to date.

This flag allows for enforcing re-regeneration, e.g. when other, non-schema specific things have changed that require a regeneration.]]> 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.]]> This feature is available in the commercial distribution only.]]> This feature is available in the commercial distribution only.]]> This feature is available in the commercial distribution only.]]> This feature is available in the commercial distribution only.]]> This feature is available in the commercial distribution only.]]> GENERATED BY DEFAULT AS IDENTITY columns should expose {@link org.jooq.DataType#readonly()} behaviour.

This feature is available in the commercial distribution only.]]> GENERATED ALWAYS AS IDENTITY columns should expose {@link org.jooq.DataType#readonly()} behaviour.

This feature is available in the commercial distribution only.]]> This feature is available in the commercial distribution only.]]> This feature is available in the commercial distribution only.]]> @java.lang.Deprecated @java.lang.Deprecated @java.lang.Deprecated @java.lang.Deprecated This feature is available in the commercial distribution only.]]> @java.lang.Deprecated @java.lang.Deprecated This feature is available in the commercial distribution only.]]> This feature is available in the commercial distribution only.]]> This feature is available in the commercial distribution only.]]> This feature is available in the commercial distribution only.]]> ROWID column should be generated.

Use this along with the synthetic primary key feature to replace existing primary key usage by ROWID usage, if this makes sense for your {@link UpdatableRecord}.]]> BY DEFAULT generation mode.]]> ALWAYS generation mode.]]> 'some string', not some string]]> SELECT DISTINCT matched_column FROM matched_table).]]> CHECK constraints for the matched column, if possible.]]> This feature is available in the commercial distribution only.]]> This feature is available in the commercial distribution only.]]> This feature is available in the commercial distribution only.]]> void.]]> @java.lang.Deprecated @java.lang.Deprecated @java.lang.Deprecated @java.lang.Deprecated @java.lang.Deprecated @java.lang.Deprecated @java.lang.Deprecated @java.lang.Deprecated @java.lang.Deprecated @java.lang.Deprecated @java.lang.Deprecated @java.lang.Deprecated @java.lang.Deprecated @java.lang.Deprecated @java.lang.Deprecated @java.lang.Deprecated @java.lang.Deprecated @java.lang.Deprecated @java.lang.Deprecated @java.lang.Deprecated @java.lang.Deprecated @java.lang.Deprecated @java.lang.Deprecated @java.lang.Deprecated @java.lang.Deprecated @java.lang.Deprecated @java.lang.Deprecated @java.lang.Deprecated @java.lang.Deprecated @java.lang.Deprecated @java.lang.Deprecated @java.lang.Deprecated @java.lang.Deprecated @java.lang.Deprecated @java.lang.Deprecated @java.lang.Deprecated @java.lang.Deprecated @java.lang.Deprecated @java.lang.Deprecated @java.lang.Deprecated @java.lang.Deprecated If provided, {@link #getName()} will be ignored, and either {@link #getConverter()} or {@link #getBinding()} is required]]> This has no effect on matched objects that are not columns.

This feature is available in the commercial distribution only.]]> This has no effect on matched objects that are not columns.

This feature is available in the commercial distribution only.]]> This flag produces a {@link #generator} configuration, so it cannot be combined with a custom generator. The different audit flags are mutually exclusive.

This feature is available in the commercial distribution only.]]> <T, U> type variables as well as Class<T> and Class<U> constructor arguments.]]><T, U> type variables as well as Class<T> and Class<U> constructor arguments.]]> When a child table has only one {@link org.jooq.meta.ForeignKeyDefinition} towards a parent table, then that path is "unambiguous." In that case, some {@link GeneratorStrategy} implementations may choose to use the parent table's {@link org.jooq.meta.TableDefinition} for implementations of {@link org.jooq.codegen.GeneratorStrategy#getJavaMethodName(Definition)}, instead of the {@link org.jooq.meta.ForeignKeyDefinition}, e.g. for implicit join paths.

This flag allows for turning off this default behaviour.]]> @java.lang.Deprecated @java.lang.Deprecated date attribute.]]> true if {@link #constructorPropertiesAnnotation} is active).]]> true if {@link #constructorPropertiesAnnotation} is active).]]> This is a Java regular expression. Use the pipe to separate several expressions. Watch out for case-sensitivity. Depending on your database, this might be important!

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. Watch out for case-sensitivity. Depending on your database, this might be important!

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

Whitespace is ignored and comments are possible unless overridden in {@link #getRegexFlags()}.]]> @java.lang.Deprecated @java.lang.Deprecated This is a Java regular expression. Use the pipe to separate several expressions. Watch out for case-sensitivity. Depending on your database, this might be important!

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

Whitespace is ignored and comments are possible unless overridden in {@link #getRegexFlags()}.]]> setX() setters instead of setIsX() in byte code for mutable properties called isX.]]> DefaultCatalog object, which is generated by default in the absence of catalogs.]]> DefaultSchema object, which is generated by default in the absence of schemas.]]> 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+ ]]> 0.]]> https://github.com/jOOQ/jOOQ/issues/13937) for {@link org.jooq.Table#rename(org.jooq.Name)} and related overloads.]]> This feature is available in the commercial distribution only.]]> This feature is available in the commercial distribution only.]]> This feature is available in the commercial distribution only.]]> This feature is available in the commercial distribution only.]]> jOOQ may append the schema name to this package if generating multiple schemas, e.g. org.jooq.generated.schema1, org.jooq.generated.schema2]]> public visibility (explicit public in Java, nothing in Kotlin, Scala).]]> public visibility modifier is generated, where supported (no modifier is generated in Scala).]]> internal visibility modifier is generated, where supported (or public, otherwise).]]> private visibility modifier is generated. This is useful only for {@link ForcedType}, not as a global configuration.]]> Generated annotation should be detected automatically from the JDK used at code generation time.]]> javax.annotation.Generated annotation.]]> javax.annotation.processing.Generated annotation.]]> jakarta.annotation.Generated annotation.]]>