XMLDatabase
, or DDLDatabase
, or to pass to JDBC drivers.]]>Natively supported values are:
This value can be used to reverse-engineer generic JDBC DatabaseMetaData (e.g. for MS Access).
This value can be used to reverse-engineer standard jOOQ-meta XML formats.
This value can be used to reverse-engineer JPA annotated entities
You can also provide your own org.jooq.meta.Database implementation here, if your database is currently not supported]]>
dialect=ORACLE xml-file=C:\path\to\database.xml xsl-files=C:\path\to\1.xsl,C:\path\to\2.xsl
packages=com.example.entities
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()}.]]>
Synthetic primary keys will override existing primary keys.]]>
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.]]>
@deprecated This feature is deprecated as of jOOQ 3.6.0 and will be removed again in jOOQ 4.0.]]>
This will be ignored if {@link #isOutputCatalogToDefault()} is set to true]]>
This configuration element cannot be used at the same time as the {@link #getCatalogs()} configuration element.]]>
Schema versions will be generated into the {@link javax.annotation.Generated} annotation on generated artefacts.]]>
Catalog versions will be generated into the {@link javax.annotation.Generated} annotation on generated artefacts.]]>
While this flag defaults to true for most databases, it defaults to false for Oracle.]]>
If this flag is set to true, then:
Custom GeneratorStrategy implementations are unaffected]]>
java\.lang\..*
]]>