Deprecated API

Contents

• Terminally Deprecated
• Interfaces
• Classes
• Enum Classes
• Exceptions
• Annotation Interfaces
• Fields
• Methods
• Constructors
• Enum Constants

Terminally Deprecated Elements

Element	Description
org.jooq.AlterDatabaseFinalStep	- [#11329] - 3.15.0 - This type will be removed in the future. Do not reference it directly Referencing XYZ*Step types directly from client code It is usually not recommended to reference any XYZ*Step types directly from client code, or assign them to local variables. When writing dynamic SQL, creating a statement's components dynamically, and passing them to the DSL API statically is usually a better choice. See the manual's section about dynamic SQL for details: https://www.jooq.org/doc/latest/manual/sql-building/dynamic-sql. Drawbacks of referencing the XYZ*Step types directly: They're operating on mutable implementations (as of jOOQ 3.x) They're less composable and not easy to get right when dynamic SQL gets complex They're less readable They might have binary incompatible changes between minor releases
org.jooq.AlterDomainFinalStep	- [#11329] - 3.15.0 - This type will be removed in the future. Do not reference it directly Referencing XYZ*Step types directly from client code It is usually not recommended to reference any XYZ*Step types directly from client code, or assign them to local variables. When writing dynamic SQL, creating a statement's components dynamically, and passing them to the DSL API statically is usually a better choice. See the manual's section about dynamic SQL for details: https://www.jooq.org/doc/latest/manual/sql-building/dynamic-sql. Drawbacks of referencing the XYZ*Step types directly: They're operating on mutable implementations (as of jOOQ 3.x) They're less composable and not easy to get right when dynamic SQL gets complex They're less readable They might have binary incompatible changes between minor releases
org.jooq.AlterIndexFinalStep	- [#11329] - 3.15.0 - This type will be removed in the future. Do not reference it directly Referencing XYZ*Step types directly from client code It is usually not recommended to reference any XYZ*Step types directly from client code, or assign them to local variables. When writing dynamic SQL, creating a statement's components dynamically, and passing them to the DSL API statically is usually a better choice. See the manual's section about dynamic SQL for details: https://www.jooq.org/doc/latest/manual/sql-building/dynamic-sql. Drawbacks of referencing the XYZ*Step types directly: They're operating on mutable implementations (as of jOOQ 3.x) They're less composable and not easy to get right when dynamic SQL gets complex They're less readable They might have binary incompatible changes between minor releases
org.jooq.AlterSchemaFinalStep	- [#11329] - 3.15.0 - This type will be removed in the future. Do not reference it directly Referencing XYZ*Step types directly from client code It is usually not recommended to reference any XYZ*Step types directly from client code, or assign them to local variables. When writing dynamic SQL, creating a statement's components dynamically, and passing them to the DSL API statically is usually a better choice. See the manual's section about dynamic SQL for details: https://www.jooq.org/doc/latest/manual/sql-building/dynamic-sql. Drawbacks of referencing the XYZ*Step types directly: They're operating on mutable implementations (as of jOOQ 3.x) They're less composable and not easy to get right when dynamic SQL gets complex They're less readable They might have binary incompatible changes between minor releases
org.jooq.AlterSequenceFinalStep	- [#11329] - 3.15.0 - This type will be removed in the future. Do not reference it directly Referencing XYZ*Step types directly from client code It is usually not recommended to reference any XYZ*Step types directly from client code, or assign them to local variables. When writing dynamic SQL, creating a statement's components dynamically, and passing them to the DSL API statically is usually a better choice. See the manual's section about dynamic SQL for details: https://www.jooq.org/doc/latest/manual/sql-building/dynamic-sql. Drawbacks of referencing the XYZ*Step types directly: They're operating on mutable implementations (as of jOOQ 3.x) They're less composable and not easy to get right when dynamic SQL gets complex They're less readable They might have binary incompatible changes between minor releases
org.jooq.AlterTableFinalStep	- [#11329] - 3.15.0 - This type will be removed in the future. Do not reference it directly
org.jooq.AlterTypeFinalStep	- [#11329] - 3.15.0 - This type will be removed in the future. Do not reference it directly Referencing XYZ*Step types directly from client code It is usually not recommended to reference any XYZ*Step types directly from client code, or assign them to local variables. When writing dynamic SQL, creating a statement's components dynamically, and passing them to the DSL API statically is usually a better choice. See the manual's section about dynamic SQL for details: https://www.jooq.org/doc/latest/manual/sql-building/dynamic-sql. Drawbacks of referencing the XYZ*Step types directly: They're operating on mutable implementations (as of jOOQ 3.x) They're less composable and not easy to get right when dynamic SQL gets complex They're less readable They might have binary incompatible changes between minor releases
org.jooq.AlterViewFinalStep	- [#11329] - 3.15.0 - This type will be removed in the future. Do not reference it directly Referencing XYZ*Step types directly from client code It is usually not recommended to reference any XYZ*Step types directly from client code, or assign them to local variables. When writing dynamic SQL, creating a statement's components dynamically, and passing them to the DSL API statically is usually a better choice. See the manual's section about dynamic SQL for details: https://www.jooq.org/doc/latest/manual/sql-building/dynamic-sql. Drawbacks of referencing the XYZ*Step types directly: They're operating on mutable implementations (as of jOOQ 3.x) They're less composable and not easy to get right when dynamic SQL gets complex They're less readable They might have binary incompatible changes between minor releases
org.jooq.Clause	- 3.11.0 - [#7258] - This part of the VisitListener SPI is deprecated. There are currently no plans of replacing it. Please get in touch if you think this functionality needs to be kept in one way or another: https://github.com/jOOQ/jOOQ/issues/7258
org.jooq.CloseableResultQuery.intern(int...)	- 3.10 - [#6254] - This functionality is no longer supported and will be removed in 4.0
org.jooq.CloseableResultQuery.intern(String...)	- 3.10 - [#6254] - This functionality is no longer supported and will be removed in 4.0
org.jooq.CloseableResultQuery.intern(Field<?>...)	- 3.10 - [#6254] - This functionality is no longer supported and will be removed in 4.0
org.jooq.CloseableResultQuery.intern(Name...)	- 3.10 - [#6254] - This functionality is no longer supported and will be removed in 4.0
org.jooq.CommentOnFinalStep	- [#11329] - 3.15.0 - This type will be removed in the future. Do not reference it directly Referencing XYZ*Step types directly from client code It is usually not recommended to reference any XYZ*Step types directly from client code, or assign them to local variables. When writing dynamic SQL, creating a statement's components dynamically, and passing them to the DSL API statically is usually a better choice. See the manual's section about dynamic SQL for details: https://www.jooq.org/doc/latest/manual/sql-building/dynamic-sql. Drawbacks of referencing the XYZ*Step types directly: They're operating on mutable implementations (as of jOOQ 3.x) They're less composable and not easy to get right when dynamic SQL gets complex They're less readable They might have binary incompatible changes between minor releases
org.jooq.Comparator.supportsNulls()	- 3.14.0 - [#9911] - This method is no longer supported.
org.jooq.Comparator.supportsQuantifier()	- 3.14.0 - [#9911] - This method is no longer supported.
org.jooq.Comparator.supportsSubselect()	- 3.14.0 - [#9911] - This method is no longer supported.
org.jooq.ConditionProvider	- 2.6.0 [#1881] - This type will be removed from the public API, soon. Its methods will be pushed down into extending interfaces. Do not reference this type directly.
org.jooq.Configuration.schemaMapping()	- 2.0.5 - Use Configuration.settings() instead
org.jooq.ConstraintFinalStep	- [#11329] - 3.15.0 - This type will be removed in the future. Do not reference it directly
org.jooq.Context.formatIndentLockEnd()	- [#10317] - 3.14.0 - Do not reuse this method. It will be removed without replacement.
org.jooq.Context.formatIndentLockStart()	- [#10317] - 3.14.0 - Do not reuse this method. It will be removed without replacement.
org.jooq.Context.keyword(String)	- 3.10.0 - [#4990] - Use DSL.keyword(String) instead.
org.jooq.Context.literal(String)	- 3.10.0 - [#4990] - Use any of DSL.name(String), DSL.quotedName(String) or DSL.unquotedName(String) instead.
org.jooq.Converters.of()	- [#10689] - 3.14.0 - This converter does not work. Do not use this method, use Converters.identity(Class) instead.
org.jooq.Converters.of(Converter<T, U>)	- [#10689] - 3.14.0 - This method does not provide any useful functionality and will be removed in the future.
org.jooq.CreateDatabaseFinalStep	- [#11329] - 3.15.0 - This type will be removed in the future. Do not reference it directly Referencing XYZ*Step types directly from client code It is usually not recommended to reference any XYZ*Step types directly from client code, or assign them to local variables. When writing dynamic SQL, creating a statement's components dynamically, and passing them to the DSL API statically is usually a better choice. See the manual's section about dynamic SQL for details: https://www.jooq.org/doc/latest/manual/sql-building/dynamic-sql. Drawbacks of referencing the XYZ*Step types directly: They're operating on mutable implementations (as of jOOQ 3.x) They're less composable and not easy to get right when dynamic SQL gets complex They're less readable They might have binary incompatible changes between minor releases
org.jooq.CreateDomainFinalStep	- [#11329] - 3.15.0 - This type will be removed in the future. Do not reference it directly Referencing XYZ*Step types directly from client code It is usually not recommended to reference any XYZ*Step types directly from client code, or assign them to local variables. When writing dynamic SQL, creating a statement's components dynamically, and passing them to the DSL API statically is usually a better choice. See the manual's section about dynamic SQL for details: https://www.jooq.org/doc/latest/manual/sql-building/dynamic-sql. Drawbacks of referencing the XYZ*Step types directly: They're operating on mutable implementations (as of jOOQ 3.x) They're less composable and not easy to get right when dynamic SQL gets complex They're less readable They might have binary incompatible changes between minor releases
org.jooq.CreateIndexFinalStep	- [#11329] - 3.15.0 - This type will be removed in the future. Do not reference it directly Referencing XYZ*Step types directly from client code It is usually not recommended to reference any XYZ*Step types directly from client code, or assign them to local variables. When writing dynamic SQL, creating a statement's components dynamically, and passing them to the DSL API statically is usually a better choice. See the manual's section about dynamic SQL for details: https://www.jooq.org/doc/latest/manual/sql-building/dynamic-sql. Drawbacks of referencing the XYZ*Step types directly: They're operating on mutable implementations (as of jOOQ 3.x) They're less composable and not easy to get right when dynamic SQL gets complex They're less readable They might have binary incompatible changes between minor releases
org.jooq.CreateSchemaFinalStep	- [#11329] - 3.15.0 - This type will be removed in the future. Do not reference it directly Referencing XYZ*Step types directly from client code It is usually not recommended to reference any XYZ*Step types directly from client code, or assign them to local variables. When writing dynamic SQL, creating a statement's components dynamically, and passing them to the DSL API statically is usually a better choice. See the manual's section about dynamic SQL for details: https://www.jooq.org/doc/latest/manual/sql-building/dynamic-sql. Drawbacks of referencing the XYZ*Step types directly: They're operating on mutable implementations (as of jOOQ 3.x) They're less composable and not easy to get right when dynamic SQL gets complex They're less readable They might have binary incompatible changes between minor releases
org.jooq.CreateSequenceFinalStep	- [#11329] - 3.15.0 - This type will be removed in the future. Do not reference it directly Referencing XYZ*Step types directly from client code It is usually not recommended to reference any XYZ*Step types directly from client code, or assign them to local variables. When writing dynamic SQL, creating a statement's components dynamically, and passing them to the DSL API statically is usually a better choice. See the manual's section about dynamic SQL for details: https://www.jooq.org/doc/latest/manual/sql-building/dynamic-sql. Drawbacks of referencing the XYZ*Step types directly: They're operating on mutable implementations (as of jOOQ 3.x) They're less composable and not easy to get right when dynamic SQL gets complex They're less readable They might have binary incompatible changes between minor releases
org.jooq.CreateTableFinalStep	- [#11329] - 3.15.0 - This type will be removed in the future. Do not reference it directly Referencing XYZ*Step types directly from client code It is usually not recommended to reference any XYZ*Step types directly from client code, or assign them to local variables. When writing dynamic SQL, creating a statement's components dynamically, and passing them to the DSL API statically is usually a better choice. See the manual's section about dynamic SQL for details: https://www.jooq.org/doc/latest/manual/sql-building/dynamic-sql. Drawbacks of referencing the XYZ*Step types directly: They're operating on mutable implementations (as of jOOQ 3.x) They're less composable and not easy to get right when dynamic SQL gets complex They're less readable They might have binary incompatible changes between minor releases
org.jooq.CreateTypeFinalStep	- [#11329] - 3.15.0 - This type will be removed in the future. Do not reference it directly
org.jooq.CreateViewFinalStep	- [#11329] - 3.15.0 - This type will be removed in the future. Do not reference it directly
org.jooq.Cursor.fetch(int)	- 3.10 - [#6363] - Use Cursor.fetchNext(int) instead.
org.jooq.Cursor.fetchInto(H)	- 3.15.0 - [#11902] - Use Iterable.forEach(Consumer) based methods, instead.
org.jooq.Cursor.fetchNextInto(H)	- 3.15.0 - [#11902] - Use Iterable.forEach(Consumer) based methods, instead.
org.jooq.Cursor.fetchOne()	- 3.10 - [#6363] - Use Cursor.fetchNext() instead.
org.jooq.Cursor.fetchOne(RecordMapper<? super R, E>)	- 3.10 - [#6363] - Use Cursor.fetchNext(RecordMapper) instead.
org.jooq.Cursor.fetchOneInto(H)	- 3.10 - [#6363] - Use Cursor.fetchNextInto(RecordHandler) instead.
org.jooq.Cursor.fetchOneInto(Class<? extends E>)	- 3.10 - [#6363] - Use Cursor.fetchNextInto(Class) instead.
org.jooq.Cursor.fetchOneInto(Table<Z>)	- 3.10 - [#6363] - Use Cursor.fetchNextInto(Table) instead.
org.jooq.Cursor.fetchOptional()	- 3.10 - [#6363] - Use Cursor.fetchNextOptional() instead.
org.jooq.Cursor.fetchOptional(RecordMapper<? super R, E>)	- 3.10 - [#6363] - Use Cursor.fetchNextOptional(RecordMapper) instead.
org.jooq.Cursor.fetchOptionalInto(Class<? extends E>)	- 3.10 - [#6363] - Use Cursor.fetchNextOptionalInto(Class) instead.
org.jooq.Cursor.fetchOptionalInto(Table<Z>)	- 3.10 - [#6363] - Use Cursor.fetchNextOptionalInto(Table) instead.
org.jooq.DataType.defaulted(boolean)	- [#3852] - 3.8.0 - Use DataType.defaultValue(Field) instead.
org.jooq.DeleteFinalStep	- [#11329] - 3.15.0 - This type will be removed in the future. Do not reference it directly
org.jooq.DropDatabaseFinalStep	- [#11329] - 3.15.0 - This type will be removed in the future. Do not reference it directly Referencing XYZ*Step types directly from client code It is usually not recommended to reference any XYZ*Step types directly from client code, or assign them to local variables. When writing dynamic SQL, creating a statement's components dynamically, and passing them to the DSL API statically is usually a better choice. See the manual's section about dynamic SQL for details: https://www.jooq.org/doc/latest/manual/sql-building/dynamic-sql. Drawbacks of referencing the XYZ*Step types directly: They're operating on mutable implementations (as of jOOQ 3.x) They're less composable and not easy to get right when dynamic SQL gets complex They're less readable They might have binary incompatible changes between minor releases
org.jooq.DropDomainFinalStep	- [#11329] - 3.15.0 - This type will be removed in the future. Do not reference it directly Referencing XYZ*Step types directly from client code It is usually not recommended to reference any XYZ*Step types directly from client code, or assign them to local variables. When writing dynamic SQL, creating a statement's components dynamically, and passing them to the DSL API statically is usually a better choice. See the manual's section about dynamic SQL for details: https://www.jooq.org/doc/latest/manual/sql-building/dynamic-sql. Drawbacks of referencing the XYZ*Step types directly: They're operating on mutable implementations (as of jOOQ 3.x) They're less composable and not easy to get right when dynamic SQL gets complex They're less readable They might have binary incompatible changes between minor releases
org.jooq.DropIndexFinalStep	- [#11329] - 3.15.0 - This type will be removed in the future. Do not reference it directly Referencing XYZ*Step types directly from client code It is usually not recommended to reference any XYZ*Step types directly from client code, or assign them to local variables. When writing dynamic SQL, creating a statement's components dynamically, and passing them to the DSL API statically is usually a better choice. See the manual's section about dynamic SQL for details: https://www.jooq.org/doc/latest/manual/sql-building/dynamic-sql. Drawbacks of referencing the XYZ*Step types directly: They're operating on mutable implementations (as of jOOQ 3.x) They're less composable and not easy to get right when dynamic SQL gets complex They're less readable They might have binary incompatible changes between minor releases
org.jooq.DropSchemaFinalStep	- [#11329] - 3.15.0 - This type will be removed in the future. Do not reference it directly Referencing XYZ*Step types directly from client code It is usually not recommended to reference any XYZ*Step types directly from client code, or assign them to local variables. When writing dynamic SQL, creating a statement's components dynamically, and passing them to the DSL API statically is usually a better choice. See the manual's section about dynamic SQL for details: https://www.jooq.org/doc/latest/manual/sql-building/dynamic-sql. Drawbacks of referencing the XYZ*Step types directly: They're operating on mutable implementations (as of jOOQ 3.x) They're less composable and not easy to get right when dynamic SQL gets complex They're less readable They might have binary incompatible changes between minor releases
org.jooq.DropSequenceFinalStep	- [#11329] - 3.15.0 - This type will be removed in the future. Do not reference it directly Referencing XYZ*Step types directly from client code It is usually not recommended to reference any XYZ*Step types directly from client code, or assign them to local variables. When writing dynamic SQL, creating a statement's components dynamically, and passing them to the DSL API statically is usually a better choice. See the manual's section about dynamic SQL for details: https://www.jooq.org/doc/latest/manual/sql-building/dynamic-sql. Drawbacks of referencing the XYZ*Step types directly: They're operating on mutable implementations (as of jOOQ 3.x) They're less composable and not easy to get right when dynamic SQL gets complex They're less readable They might have binary incompatible changes between minor releases
org.jooq.DropTableFinalStep	- [#11329] - 3.15.0 - This type will be removed in the future. Do not reference it directly Referencing XYZ*Step types directly from client code It is usually not recommended to reference any XYZ*Step types directly from client code, or assign them to local variables. When writing dynamic SQL, creating a statement's components dynamically, and passing them to the DSL API statically is usually a better choice. See the manual's section about dynamic SQL for details: https://www.jooq.org/doc/latest/manual/sql-building/dynamic-sql. Drawbacks of referencing the XYZ*Step types directly: They're operating on mutable implementations (as of jOOQ 3.x) They're less composable and not easy to get right when dynamic SQL gets complex They're less readable They might have binary incompatible changes between minor releases
org.jooq.DropTypeFinalStep	- [#11329] - 3.15.0 - This type will be removed in the future. Do not reference it directly
org.jooq.DropViewFinalStep	- [#11329] - 3.15.0 - This type will be removed in the future. Do not reference it directly Referencing XYZ*Step types directly from client code It is usually not recommended to reference any XYZ*Step types directly from client code, or assign them to local variables. When writing dynamic SQL, creating a statement's components dynamically, and passing them to the DSL API statically is usually a better choice. See the manual's section about dynamic SQL for details: https://www.jooq.org/doc/latest/manual/sql-building/dynamic-sql. Drawbacks of referencing the XYZ*Step types directly: They're operating on mutable implementations (as of jOOQ 3.x) They're less composable and not easy to get right when dynamic SQL gets complex They're less readable They might have binary incompatible changes between minor releases
org.jooq.DSLContext.bindContext(PreparedStatement)	- [#6280] - 3.10 - Do not reuse this method. It will be completely internal with jOOQ 4.0
org.jooq.DSLContext.createOrReplaceView(String, BiFunction<? super Field<?>, ? super Integer, ? extends String>)	- 3.14.0 - [#10156] - These methods will be removed without replacement from a future jOOQ. They offer convenience that is unidiomatic for jOOQ's DSL, without offering functionality that would not be possible otherwise - yet they add complexity in jOOQ's internals.
org.jooq.DSLContext.createOrReplaceView(String, Function<? super Field<?>, ? extends String>)	- 3.14.0 - [#10156] - These methods will be removed without replacement from a future jOOQ. They offer convenience that is unidiomatic for jOOQ's DSL, without offering functionality that would not be possible otherwise - yet they add complexity in jOOQ's internals.
org.jooq.DSLContext.createOrReplaceView(Name, BiFunction<? super Field<?>, ? super Integer, ? extends Name>)	- 3.14.0 - [#10156] - These methods will be removed without replacement from a future jOOQ. They offer convenience that is unidiomatic for jOOQ's DSL, without offering functionality that would not be possible otherwise - yet they add complexity in jOOQ's internals.
org.jooq.DSLContext.createOrReplaceView(Name, Function<? super Field<?>, ? extends Name>)	- 3.14.0 - [#10156] - These methods will be removed without replacement from a future jOOQ. They offer convenience that is unidiomatic for jOOQ's DSL, without offering functionality that would not be possible otherwise - yet they add complexity in jOOQ's internals.
org.jooq.DSLContext.createOrReplaceView(Table<?>, BiFunction<? super Field<?>, ? super Integer, ? extends Field<?>>)	- 3.14.0 - [#10156] - These methods will be removed without replacement from a future jOOQ. They offer convenience that is unidiomatic for jOOQ's DSL, without offering functionality that would not be possible otherwise - yet they add complexity in jOOQ's internals.
org.jooq.DSLContext.createOrReplaceView(Table<?>, Function<? super Field<?>, ? extends Field<?>>)	- 3.14.0 - [#10156] - These methods will be removed without replacement from a future jOOQ. They offer convenience that is unidiomatic for jOOQ's DSL, without offering functionality that would not be possible otherwise - yet they add complexity in jOOQ's internals.
org.jooq.DSLContext.createView(String, BiFunction<? super Field<?>, ? super Integer, ? extends String>)	- 3.14.0 - [#10156] - These methods will be removed without replacement from a future jOOQ. They offer convenience that is unidiomatic for jOOQ's DSL, without offering functionality that would not be possible otherwise - yet they add complexity in jOOQ's internals.
org.jooq.DSLContext.createView(String, Function<? super Field<?>, ? extends String>)	- 3.14.0 - [#10156] - These methods will be removed without replacement from a future jOOQ. They offer convenience that is unidiomatic for jOOQ's DSL, without offering functionality that would not be possible otherwise - yet they add complexity in jOOQ's internals.
org.jooq.DSLContext.createView(Name, BiFunction<? super Field<?>, ? super Integer, ? extends Name>)	- 3.14.0 - [#10156] - These methods will be removed without replacement from a future jOOQ. They offer convenience that is unidiomatic for jOOQ's DSL, without offering functionality that would not be possible otherwise - yet they add complexity in jOOQ's internals.
org.jooq.DSLContext.createView(Name, Function<? super Field<?>, ? extends Name>)	- 3.14.0 - [#10156] - These methods will be removed without replacement from a future jOOQ. They offer convenience that is unidiomatic for jOOQ's DSL, without offering functionality that would not be possible otherwise - yet they add complexity in jOOQ's internals.
org.jooq.DSLContext.createView(Table<?>, BiFunction<? super Field<?>, ? super Integer, ? extends Field<?>>)	- 3.14.0 - [#10156] - These methods will be removed without replacement from a future jOOQ. They offer convenience that is unidiomatic for jOOQ's DSL, without offering functionality that would not be possible otherwise - yet they add complexity in jOOQ's internals.
org.jooq.DSLContext.createView(Table<?>, Function<? super Field<?>, ? extends Field<?>>)	- 3.14.0 - [#10156] - These methods will be removed without replacement from a future jOOQ. They offer convenience that is unidiomatic for jOOQ's DSL, without offering functionality that would not be possible otherwise - yet they add complexity in jOOQ's internals.
org.jooq.DSLContext.createViewIfNotExists(String, BiFunction<? super Field<?>, ? super Integer, ? extends String>)	- 3.14.0 - [#10156] - These methods will be removed without replacement from a future jOOQ. They offer convenience that is unidiomatic for jOOQ's DSL, without offering functionality that would not be possible otherwise - yet they add complexity in jOOQ's internals.
org.jooq.DSLContext.createViewIfNotExists(String, Function<? super Field<?>, ? extends String>)	- 3.14.0 - [#10156] - These methods will be removed without replacement from a future jOOQ. They offer convenience that is unidiomatic for jOOQ's DSL, without offering functionality that would not be possible otherwise - yet they add complexity in jOOQ's internals.
org.jooq.DSLContext.createViewIfNotExists(Name, BiFunction<? super Field<?>, ? super Integer, ? extends Name>)	- 3.14.0 - [#10156] - These methods will be removed without replacement from a future jOOQ. They offer convenience that is unidiomatic for jOOQ's DSL, without offering functionality that would not be possible otherwise - yet they add complexity in jOOQ's internals.
org.jooq.DSLContext.createViewIfNotExists(Name, Function<? super Field<?>, ? extends Name>)	- 3.14.0 - [#10156] - These methods will be removed without replacement from a future jOOQ. They offer convenience that is unidiomatic for jOOQ's DSL, without offering functionality that would not be possible otherwise - yet they add complexity in jOOQ's internals.
org.jooq.DSLContext.createViewIfNotExists(Table<?>, BiFunction<? super Field<?>, ? super Integer, ? extends Field<?>>)	- 3.14.0 - [#10156] - These methods will be removed without replacement from a future jOOQ. They offer convenience that is unidiomatic for jOOQ's DSL, without offering functionality that would not be possible otherwise - yet they add complexity in jOOQ's internals.
org.jooq.DSLContext.createViewIfNotExists(Table<?>, Function<? super Field<?>, ? extends Field<?>>)	- 3.14.0 - [#10156] - These methods will be removed without replacement from a future jOOQ. They offer convenience that is unidiomatic for jOOQ's DSL, without offering functionality that would not be possible otherwise - yet they add complexity in jOOQ's internals.
org.jooq.DSLContext.mergeInto(Table<R>, Collection<? extends Field<?>>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.DSLContext.mergeInto(Table<R>, Field<?>...)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.DSLContext.mergeInto(Table<R>, Field<T1>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.DSLContext.mergeInto(Table<R>, Field<T1>, Field<T2>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.DSLContext.mergeInto(Table<R>, Field<T1>, Field<T2>, Field<T3>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.DSLContext.mergeInto(Table<R>, Field<T1>, Field<T2>, Field<T3>, Field<T4>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.DSLContext.mergeInto(Table<R>, Field<T1>, Field<T2>, Field<T3>, Field<T4>, Field<T5>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.DSLContext.mergeInto(Table<R>, Field<T1>, Field<T2>, Field<T3>, Field<T4>, Field<T5>, Field<T6>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.DSLContext.mergeInto(Table<R>, Field<T1>, Field<T2>, Field<T3>, Field<T4>, Field<T5>, Field<T6>, Field<T7>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.DSLContext.mergeInto(Table<R>, Field<T1>, Field<T2>, Field<T3>, Field<T4>, Field<T5>, Field<T6>, Field<T7>, Field<T8>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.DSLContext.mergeInto(Table<R>, Field<T1>, Field<T2>, Field<T3>, Field<T4>, Field<T5>, Field<T6>, Field<T7>, Field<T8>, Field<T9>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.DSLContext.mergeInto(Table<R>, Field<T1>, Field<T2>, Field<T3>, Field<T4>, Field<T5>, Field<T6>, Field<T7>, Field<T8>, Field<T9>, Field<T10>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.DSLContext.mergeInto(Table<R>, Field<T1>, Field<T2>, Field<T3>, Field<T4>, Field<T5>, Field<T6>, Field<T7>, Field<T8>, Field<T9>, Field<T10>, Field<T11>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.DSLContext.mergeInto(Table<R>, Field<T1>, Field<T2>, Field<T3>, Field<T4>, Field<T5>, Field<T6>, Field<T7>, Field<T8>, Field<T9>, Field<T10>, Field<T11>, Field<T12>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.DSLContext.mergeInto(Table<R>, Field<T1>, Field<T2>, Field<T3>, Field<T4>, Field<T5>, Field<T6>, Field<T7>, Field<T8>, Field<T9>, Field<T10>, Field<T11>, Field<T12>, Field<T13>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.DSLContext.mergeInto(Table<R>, Field<T1>, Field<T2>, Field<T3>, Field<T4>, Field<T5>, Field<T6>, Field<T7>, Field<T8>, Field<T9>, Field<T10>, Field<T11>, Field<T12>, Field<T13>, Field<T14>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.DSLContext.mergeInto(Table<R>, Field<T1>, Field<T2>, Field<T3>, Field<T4>, Field<T5>, Field<T6>, Field<T7>, Field<T8>, Field<T9>, Field<T10>, Field<T11>, Field<T12>, Field<T13>, Field<T14>, Field<T15>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.DSLContext.mergeInto(Table<R>, Field<T1>, Field<T2>, Field<T3>, Field<T4>, Field<T5>, Field<T6>, Field<T7>, Field<T8>, Field<T9>, Field<T10>, Field<T11>, Field<T12>, Field<T13>, Field<T14>, Field<T15>, Field<T16>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.DSLContext.mergeInto(Table<R>, Field<T1>, Field<T2>, Field<T3>, Field<T4>, Field<T5>, Field<T6>, Field<T7>, Field<T8>, Field<T9>, Field<T10>, Field<T11>, Field<T12>, Field<T13>, Field<T14>, Field<T15>, Field<T16>, Field<T17>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.DSLContext.mergeInto(Table<R>, Field<T1>, Field<T2>, Field<T3>, Field<T4>, Field<T5>, Field<T6>, Field<T7>, Field<T8>, Field<T9>, Field<T10>, Field<T11>, Field<T12>, Field<T13>, Field<T14>, Field<T15>, Field<T16>, Field<T17>, Field<T18>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.DSLContext.mergeInto(Table<R>, Field<T1>, Field<T2>, Field<T3>, Field<T4>, Field<T5>, Field<T6>, Field<T7>, Field<T8>, Field<T9>, Field<T10>, Field<T11>, Field<T12>, Field<T13>, Field<T14>, Field<T15>, Field<T16>, Field<T17>, Field<T18>, Field<T19>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.DSLContext.mergeInto(Table<R>, Field<T1>, Field<T2>, Field<T3>, Field<T4>, Field<T5>, Field<T6>, Field<T7>, Field<T8>, Field<T9>, Field<T10>, Field<T11>, Field<T12>, Field<T13>, Field<T14>, Field<T15>, Field<T16>, Field<T17>, Field<T18>, Field<T19>, Field<T20>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.DSLContext.mergeInto(Table<R>, Field<T1>, Field<T2>, Field<T3>, Field<T4>, Field<T5>, Field<T6>, Field<T7>, Field<T8>, Field<T9>, Field<T10>, Field<T11>, Field<T12>, Field<T13>, Field<T14>, Field<T15>, Field<T16>, Field<T17>, Field<T18>, Field<T19>, Field<T20>, Field<T21>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.DSLContext.mergeInto(Table<R>, Field<T1>, Field<T2>, Field<T3>, Field<T4>, Field<T5>, Field<T6>, Field<T7>, Field<T8>, Field<T9>, Field<T10>, Field<T11>, Field<T12>, Field<T13>, Field<T14>, Field<T15>, Field<T16>, Field<T17>, Field<T18>, Field<T19>, Field<T20>, Field<T21>, Field<T22>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.DSLContext.renderContext()	- [#6280] - 3.10 - Do not reuse this method. It will be completely internal with jOOQ 4.0
org.jooq.DSLContext.with(String, BiFunction<? super Field<?>, ? super Integer, ? extends String>)	- 3.14.0 - [#10156] - These methods will be removed without replacement from a future jOOQ. They offer convenience that is unidiomatic for jOOQ's DSL, without offering functionality that would not be possible otherwise - yet they add complexity in jOOQ's internals.
org.jooq.DSLContext.with(String, Function<? super Field<?>, ? extends String>)	- 3.14.0 - [#10156] - These methods will be removed without replacement from a future jOOQ. They offer convenience that is unidiomatic for jOOQ's DSL, without offering functionality that would not be possible otherwise - yet they add complexity in jOOQ's internals.
org.jooq.DSLContext.withRecursive(String, BiFunction<? super Field<?>, ? super Integer, ? extends String>)	- 3.14.0 - [#10156] - These methods will be removed without replacement from a future jOOQ. They offer convenience that is unidiomatic for jOOQ's DSL, without offering functionality that would not be possible otherwise - yet they add complexity in jOOQ's internals.
org.jooq.DSLContext.withRecursive(String, Function<? super Field<?>, ? extends String>)	- 3.14.0 - [#10156] - These methods will be removed without replacement from a future jOOQ. They offer convenience that is unidiomatic for jOOQ's DSL, without offering functionality that would not be possible otherwise - yet they add complexity in jOOQ's internals.
org.jooq.Field.abs()	- 3.11 - [#7538] - Use DSL.abs(Field) instead.
org.jooq.Field.acos()	- 3.11 - [#7538] - Use DSL.acos(Field) instead.
org.jooq.Field.as(Function<? super Field<T>, ? extends String>)	- 3.14.0 - [#10156] - These methods will be removed without replacement from a future jOOQ. They offer convenience that is unidiomatic for jOOQ's DSL, without offering functionality that would not be possible otherwise - yet they add complexity in jOOQ's internals.
org.jooq.Field.ascii()	- 3.13 - [#9407] - Use DSL.ascii(Field) instead.
org.jooq.Field.asin()	- 3.11 - [#7538] - Use DSL.asin(Field) instead.
org.jooq.Field.atan()	- 3.11 - [#7538] - Use DSL.atan(Field) instead.
org.jooq.Field.atan2(Number)	- 3.11 - [#7538] - Use DSL.atan2(Field, Number) instead.
org.jooq.Field.atan2(Field<? extends Number>)	- 3.11 - [#7538] - Use DSL.atan2(Field, Field) instead.
org.jooq.Field.avg()	- 3.11 - [#7538] - Use DSL.avg(Field) instead.
org.jooq.Field.avgOver()	- 3.11 - [#7538] - Use DSL.avg(Field) instead.
org.jooq.Field.bitLength()	- 3.13 - [#9407] - Use DSL.bitLength(Field) instead.
org.jooq.Field.ceil()	- 3.11 - [#7538] - Use DSL.ceil(Field) instead.
org.jooq.Field.charLength()	- 3.13 - [#9407] - Use DSL.charLength(Field) instead.
org.jooq.Field.coalesce(Field<T>, Field<?>...)	- 3.13 - [#9407] - Use DSL.coalesce(Field, Field...) instead.
org.jooq.Field.coalesce(T, T...)	- 3.13 - [#9407] - Use DSL.coalesce(Object, Object...) instead.
org.jooq.Field.cos()	- 3.11 - [#7538] - Use DSL.cos(Field) instead.
org.jooq.Field.cosh()	- 3.11 - [#7538] - Use DSL.cosh(Field) instead.
org.jooq.Field.cot()	- 3.11 - [#7538] - Use DSL.cot(Field) instead.
org.jooq.Field.coth()	- 3.11 - [#7538] - Use DSL.coth(Field) instead.
org.jooq.Field.count()	- 3.11 - [#7538] - Use DSL.count(Field) instead.
org.jooq.Field.countDistinct()	- 3.11 - [#7538] - Use DSL.countDistinct(Field) instead.
org.jooq.Field.countOver()	- 3.11 - [#7538] - Use DSL.count(Field) instead.
org.jooq.Field.decode(Field<T>, Field<Z>)	- 3.13 - [#9407] - Use DSL.decode(Field, Field, Field) instead.
org.jooq.Field.decode(Field<T>, Field<Z>, Field<?>...)	- 3.13 - [#9407] - Use DSL.decode(Field, Field, Field, Field...) instead.
org.jooq.Field.decode(T, Z)	- 3.13 - [#9407] - Use DSL.decode(Object, Object, Object) instead.
org.jooq.Field.decode(T, Z, Object...)	- 3.13 - [#9407] - Use DSL.decode(Object, Object, Object, Object...) instead.
org.jooq.Field.deg()	- 3.11 - [#7538] - Use DSL.deg(Field) instead.
org.jooq.Field.exp()	- 3.11 - [#7538] - Use DSL.exp(Field) instead.
org.jooq.Field.extract(DatePart)	- 3.11 - [#7538] - Use DSL.extract(Field, DatePart) instead.
org.jooq.Field.firstValue()	- 3.11 - [#7538] - Use DSL.firstValue(Field) instead.
org.jooq.Field.floor()	- 3.11 - [#7538] - Use DSL.floor(Field) instead.
org.jooq.Field.greatest(Field<?>...)	- 3.11 - [#7538] - Use DSL.greatest(Field, Field...) instead.
org.jooq.Field.greatest(T...)	- 3.11 - [#7538] - Use DSL.greatest(Field, Field...) instead.
org.jooq.Field.lag()	- 3.11 - [#7538] - Use DSL.lag(Field) instead.
org.jooq.Field.lag(int)	- 3.11 - [#7538] - Use DSL.lag(Field, int) instead.
org.jooq.Field.lag(int, Field<T>)	- 3.11 - [#7538] - Use DSL.lag(Field, int, Field) instead.
org.jooq.Field.lag(int, T)	- 3.11 - [#7538] - Use DSL.lag(Field, int, Object) instead.
org.jooq.Field.lastValue()	- 3.11 - [#7538] - Use DSL.lastValue(Field) instead.
org.jooq.Field.lead()	- 3.11 - [#7538] - Use DSL.lead(Field) instead.
org.jooq.Field.lead(int)	- 3.11 - [#7538] - Use DSL.lead(Field, int) instead.
org.jooq.Field.lead(int, Field<T>)	- 3.11 - [#7538] - Use DSL.lead(Field, int, Field) instead.
org.jooq.Field.lead(int, T)	- 3.11 - [#7538] - Use DSL.lead(Field, int, Object) instead.
org.jooq.Field.least(Field<?>...)	- 3.11 - [#7538] - Use DSL.least(Field, Field...) instead.
org.jooq.Field.least(T...)	- 3.11 - [#7538] - Use DSL.least(Field, Field...) instead.
org.jooq.Field.length()	- 3.13 - [#9407] - Use DSL.length(Field) instead.
org.jooq.Field.ln()	- 3.11 - [#7538] - Use DSL.ln(Field) instead.
org.jooq.Field.log(int)	- 3.11 - [#7538] - Use DSL.log(Field, int) instead.
org.jooq.Field.lower()	- 3.13 - [#9407] - Use DSL.lower(Field) instead.
org.jooq.Field.lpad(int)	- 3.13 - [#9407] - Use DSL.lpad(Field, int) instead.
org.jooq.Field.lpad(int, char)	- 3.13 - [#9407] - Use DSL.lpad(Field, int, char) instead.
org.jooq.Field.lpad(Field<? extends Number>)	- 3.13 - [#9407] - Use DSL.lpad(Field, Field) instead.
org.jooq.Field.lpad(Field<? extends Number>, Field<String>)	- 3.13 - [#9407] - Use DSL.lpad(Field, Field, Field) instead.
org.jooq.Field.ltrim()	- 3.13 - [#9407] - Use DSL.ltrim(Field) instead.
org.jooq.Field.max()	- 3.11 - [#7538] - Use DSL.max(Field) instead.
org.jooq.Field.maxOver()	- 3.11 - [#7538] - Use DSL.max(Field) instead.
org.jooq.Field.median()	- 3.11 - [#7538] - Use DSL.median(Field) instead.
org.jooq.Field.min()	- 3.11 - [#7538] - Use DSL.min(Field) instead.
org.jooq.Field.minOver()	- 3.11 - [#7538] - Use DSL.min(Field) instead.
org.jooq.Field.nullif(Field<T>)	- 3.13 - [#9407] - Use DSL.nullif(Field, Field) instead.
org.jooq.Field.nullif(T)	- 3.13 - [#9407] - Use DSL.nullif(Field, Object) instead.
org.jooq.Field.nvl(Field<T>)	- 3.13 - [#9407] - Use DSL.nvl(Field, Field) instead.
org.jooq.Field.nvl(T)	- 3.13 - [#9407] - Use DSL.nvl(Field, Object) instead.
org.jooq.Field.nvl2(Field<Z>, Field<Z>)	- 3.13 - [#9407] - Use DSL.nvl2(Field, Field, Field) instead.
org.jooq.Field.nvl2(Z, Z)	- 3.13 - [#9407] - Use DSL.nvl2(Field, Object, Object) instead.
org.jooq.Field.octetLength()	- 3.13 - [#9407] - Use DSL.octetLength(Field) instead.
org.jooq.Field.position(String)	- 3.13 - [#9407] - Use DSL.position(Field, String) instead.
org.jooq.Field.position(Field<String>)	- 3.13 - [#9407] - Use DSL.position(Field, Field) instead.
org.jooq.Field.rad()	- 3.11 - [#7538] - Use DSL.rad(Field) instead.
org.jooq.Field.repeat(Number)	- 3.13 - [#9407] - Use DSL.repeat(Field, int) instead.
org.jooq.Field.repeat(Field<? extends Number>)	- 3.13 - [#9407] - Use DSL.repeat(Field, Field) instead.
org.jooq.Field.replace(String)	- 3.13 - [#9407] - Use DSL.replace(Field, String) instead.
org.jooq.Field.replace(String, String)	- 3.13 - [#9407] - Use DSL.replace(Field, String, String) instead.
org.jooq.Field.replace(Field<String>)	- 3.13 - [#9407] - Use DSL.replace(Field, Field) instead.
org.jooq.Field.replace(Field<String>, Field<String>)	- 3.13 - [#9407] - Use DSL.replace(Field, Field, Field) instead.
org.jooq.Field.round()	- 3.11 - [#7538] - Use DSL.round(Field) instead.
org.jooq.Field.round(int)	- 3.11 - [#7538] - Use DSL.round(Field, int) instead.
org.jooq.Field.rpad(int)	- 3.13 - [#9407] - Use DSL.rpad(Field, int) instead.
org.jooq.Field.rpad(int, char)	- 3.13 - [#9407] - Use DSL.rpad(Field, int, char) instead.
org.jooq.Field.rpad(Field<? extends Number>)	- 3.13 - [#9407] - Use DSL.rpad(Field, Field) instead.
org.jooq.Field.rpad(Field<? extends Number>, Field<String>)	- 3.13 - [#9407] - Use DSL.rpad(Field, Field, Field) instead.
org.jooq.Field.rtrim()	- 3.13 - [#9407] - Use DSL.rtrim(Field) instead.
org.jooq.Field.sign()	- 3.11 - [#7538] - Use DSL.sign(Field) instead.
org.jooq.Field.sin()	- 3.11 - [#7538] - Use DSL.sin(Field) instead.
org.jooq.Field.sinh()	- 3.11 - [#7538] - Use DSL.sinh(Field) instead.
org.jooq.Field.sqrt()	- 3.11 - [#7538] - Use DSL.sqrt(Field) instead.
org.jooq.Field.stddevPop()	- 3.11 - [#7538] - Use DSL.stddevPop(Field) instead.
org.jooq.Field.stddevPopOver()	- 3.11 - [#7538] - Use DSL.stddevPop(Field) instead.
org.jooq.Field.stddevSamp()	- 3.11 - [#7538] - Use DSL.stddevSamp(Field) instead.
org.jooq.Field.stddevSampOver()	- 3.11 - [#7538] - Use DSL.stddevSamp(Field) instead.
org.jooq.Field.substring(int)	- 3.13 - [#9407] - Use DSL.substring(Field, int) instead.
org.jooq.Field.substring(int, int)	- 3.13 - [#9407] - Use DSL.substring(Field, int, int) instead.
org.jooq.Field.substring(Field<? extends Number>)	- 3.13 - [#9407] - Use DSL.substring(Field, Field) instead.
org.jooq.Field.substring(Field<? extends Number>, Field<? extends Number>)	- 3.13 - [#9407] - Use DSL.substring(Field, Field, Field) instead.
org.jooq.Field.sum()	- 3.11 - [#7538] - Use DSL.sum(Field) instead.
org.jooq.Field.sumOver()	- 3.11 - [#7538] - Use DSL.sum(Field) instead.
org.jooq.Field.tan()	- 3.11 - [#7538] - Use DSL.tan(Field) instead.
org.jooq.Field.tanh()	- 3.11 - [#7538] - Use DSL.tanh(Field) instead.
org.jooq.Field.trim()	- 3.13 - [#9407] - Use DSL.trim(Field) instead.
org.jooq.Field.upper()	- 3.13 - [#9407] - Use DSL.upper(Field) instead.
org.jooq.Field.varPop()	- 3.11 - [#7538] - Use DSL.varPop(Field) instead.
org.jooq.Field.varPopOver()	- 3.11 - [#7538] - Use DSL.varPop(Field) instead.
org.jooq.Field.varSamp()	- 3.11 - [#7538] - Use DSL.varSamp(Field) instead.
org.jooq.Field.varSampOver()	- 3.11 - [#7538] - Use DSL.varSamp(Field) instead.
org.jooq.FieldLike.asField(Function<? super Field<T>, ? extends String>)	- 3.14.0 - [#10156] - These methods will be removed without replacement from a future jOOQ. They offer convenience that is unidiomatic for jOOQ's DSL, without offering functionality that would not be possible otherwise - yet they add complexity in jOOQ's internals.
org.jooq.GrantFinalStep	- [#11329] - 3.15.0 - This type will be removed in the future. Do not reference it directly Referencing XYZ*Step types directly from client code It is usually not recommended to reference any XYZ*Step types directly from client code, or assign them to local variables. When writing dynamic SQL, creating a statement's components dynamically, and passing them to the DSL API statically is usually a better choice. See the manual's section about dynamic SQL for details: https://www.jooq.org/doc/latest/manual/sql-building/dynamic-sql. Drawbacks of referencing the XYZ*Step types directly: They're operating on mutable implementations (as of jOOQ 3.x) They're less composable and not easy to get right when dynamic SQL gets complex They're less readable They might have binary incompatible changes between minor releases
org.jooq.impl.DefaultBinding(Converter<T, U>)	- 3.11 - [#6631] - Use DefaultBinding.binding(Converter) instead.
org.jooq.impl.DefaultDSLContext.mergeInto(Table<R>, Field<T1>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DefaultDSLContext.mergeInto(Table)
org.jooq.impl.DefaultDSLContext.mergeInto(Table<R>, Field<T1>, Field<T2>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DefaultDSLContext.mergeInto(Table)
org.jooq.impl.DefaultDSLContext.mergeInto(Table<R>, Field<T1>, Field<T2>, Field<T3>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DefaultDSLContext.mergeInto(Table)
org.jooq.impl.DefaultDSLContext.mergeInto(Table<R>, Field<T1>, Field<T2>, Field<T3>, Field<T4>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DefaultDSLContext.mergeInto(Table)
org.jooq.impl.DefaultDSLContext.mergeInto(Table<R>, Field<T1>, Field<T2>, Field<T3>, Field<T4>, Field<T5>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DefaultDSLContext.mergeInto(Table)
org.jooq.impl.DefaultDSLContext.mergeInto(Table<R>, Field<T1>, Field<T2>, Field<T3>, Field<T4>, Field<T5>, Field<T6>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DefaultDSLContext.mergeInto(Table)
org.jooq.impl.DefaultDSLContext.mergeInto(Table<R>, Field<T1>, Field<T2>, Field<T3>, Field<T4>, Field<T5>, Field<T6>, Field<T7>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DefaultDSLContext.mergeInto(Table)
org.jooq.impl.DefaultDSLContext.mergeInto(Table<R>, Field<T1>, Field<T2>, Field<T3>, Field<T4>, Field<T5>, Field<T6>, Field<T7>, Field<T8>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DefaultDSLContext.mergeInto(Table)
org.jooq.impl.DefaultDSLContext.mergeInto(Table<R>, Field<T1>, Field<T2>, Field<T3>, Field<T4>, Field<T5>, Field<T6>, Field<T7>, Field<T8>, Field<T9>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DefaultDSLContext.mergeInto(Table)
org.jooq.impl.DefaultDSLContext.mergeInto(Table<R>, Field<T1>, Field<T2>, Field<T3>, Field<T4>, Field<T5>, Field<T6>, Field<T7>, Field<T8>, Field<T9>, Field<T10>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DefaultDSLContext.mergeInto(Table)
org.jooq.impl.DefaultDSLContext.mergeInto(Table<R>, Field<T1>, Field<T2>, Field<T3>, Field<T4>, Field<T5>, Field<T6>, Field<T7>, Field<T8>, Field<T9>, Field<T10>, Field<T11>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DefaultDSLContext.mergeInto(Table)
org.jooq.impl.DefaultDSLContext.mergeInto(Table<R>, Field<T1>, Field<T2>, Field<T3>, Field<T4>, Field<T5>, Field<T6>, Field<T7>, Field<T8>, Field<T9>, Field<T10>, Field<T11>, Field<T12>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DefaultDSLContext.mergeInto(Table)
org.jooq.impl.DefaultDSLContext.mergeInto(Table<R>, Field<T1>, Field<T2>, Field<T3>, Field<T4>, Field<T5>, Field<T6>, Field<T7>, Field<T8>, Field<T9>, Field<T10>, Field<T11>, Field<T12>, Field<T13>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DefaultDSLContext.mergeInto(Table)
org.jooq.impl.DefaultDSLContext.mergeInto(Table<R>, Field<T1>, Field<T2>, Field<T3>, Field<T4>, Field<T5>, Field<T6>, Field<T7>, Field<T8>, Field<T9>, Field<T10>, Field<T11>, Field<T12>, Field<T13>, Field<T14>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DefaultDSLContext.mergeInto(Table)
org.jooq.impl.DefaultDSLContext.mergeInto(Table<R>, Field<T1>, Field<T2>, Field<T3>, Field<T4>, Field<T5>, Field<T6>, Field<T7>, Field<T8>, Field<T9>, Field<T10>, Field<T11>, Field<T12>, Field<T13>, Field<T14>, Field<T15>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DefaultDSLContext.mergeInto(Table)
org.jooq.impl.DefaultDSLContext.mergeInto(Table<R>, Field<T1>, Field<T2>, Field<T3>, Field<T4>, Field<T5>, Field<T6>, Field<T7>, Field<T8>, Field<T9>, Field<T10>, Field<T11>, Field<T12>, Field<T13>, Field<T14>, Field<T15>, Field<T16>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DefaultDSLContext.mergeInto(Table)
org.jooq.impl.DefaultDSLContext.mergeInto(Table<R>, Field<T1>, Field<T2>, Field<T3>, Field<T4>, Field<T5>, Field<T6>, Field<T7>, Field<T8>, Field<T9>, Field<T10>, Field<T11>, Field<T12>, Field<T13>, Field<T14>, Field<T15>, Field<T16>, Field<T17>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DefaultDSLContext.mergeInto(Table)
org.jooq.impl.DefaultDSLContext.mergeInto(Table<R>, Field<T1>, Field<T2>, Field<T3>, Field<T4>, Field<T5>, Field<T6>, Field<T7>, Field<T8>, Field<T9>, Field<T10>, Field<T11>, Field<T12>, Field<T13>, Field<T14>, Field<T15>, Field<T16>, Field<T17>, Field<T18>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DefaultDSLContext.mergeInto(Table)
org.jooq.impl.DefaultDSLContext.mergeInto(Table<R>, Field<T1>, Field<T2>, Field<T3>, Field<T4>, Field<T5>, Field<T6>, Field<T7>, Field<T8>, Field<T9>, Field<T10>, Field<T11>, Field<T12>, Field<T13>, Field<T14>, Field<T15>, Field<T16>, Field<T17>, Field<T18>, Field<T19>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DefaultDSLContext.mergeInto(Table)
org.jooq.impl.DefaultDSLContext.mergeInto(Table<R>, Field<T1>, Field<T2>, Field<T3>, Field<T4>, Field<T5>, Field<T6>, Field<T7>, Field<T8>, Field<T9>, Field<T10>, Field<T11>, Field<T12>, Field<T13>, Field<T14>, Field<T15>, Field<T16>, Field<T17>, Field<T18>, Field<T19>, Field<T20>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DefaultDSLContext.mergeInto(Table)
org.jooq.impl.DefaultDSLContext.mergeInto(Table<R>, Field<T1>, Field<T2>, Field<T3>, Field<T4>, Field<T5>, Field<T6>, Field<T7>, Field<T8>, Field<T9>, Field<T10>, Field<T11>, Field<T12>, Field<T13>, Field<T14>, Field<T15>, Field<T16>, Field<T17>, Field<T18>, Field<T19>, Field<T20>, Field<T21>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DefaultDSLContext.mergeInto(Table)
org.jooq.impl.DefaultDSLContext.mergeInto(Table<R>, Field<T1>, Field<T2>, Field<T3>, Field<T4>, Field<T5>, Field<T6>, Field<T7>, Field<T8>, Field<T9>, Field<T10>, Field<T11>, Field<T12>, Field<T13>, Field<T14>, Field<T15>, Field<T16>, Field<T17>, Field<T18>, Field<T19>, Field<T20>, Field<T21>, Field<T22>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DefaultDSLContext.mergeInto(Table)
org.jooq.impl.DSL.createOrReplaceView(String, Function<? super Field<?>, ? extends String>)	- 3.14.0 - [#10156] - These methods will be removed without replacement from a future jOOQ. They offer convenience that is unidiomatic for jOOQ's DSL, without offering functionality that would not be possible otherwise - yet they add complexity in jOOQ's internals.
org.jooq.impl.DSL.createOrReplaceView(Name, Function<? super Field<?>, ? extends Name>)	- 3.14.0 - [#10156] - These methods will be removed without replacement from a future jOOQ. They offer convenience that is unidiomatic for jOOQ's DSL, without offering functionality that would not be possible otherwise - yet they add complexity in jOOQ's internals.
org.jooq.impl.DSL.createOrReplaceView(Table<?>, Function<? super Field<?>, ? extends Field<?>>)	- 3.14.0 - [#10156] - These methods will be removed without replacement from a future jOOQ. They offer convenience that is unidiomatic for jOOQ's DSL, without offering functionality that would not be possible otherwise - yet they add complexity in jOOQ's internals.
org.jooq.impl.DSL.createView(String, Function<? super Field<?>, ? extends String>)	- 3.14.0 - [#10156] - These methods will be removed without replacement from a future jOOQ. They offer convenience that is unidiomatic for jOOQ's DSL, without offering functionality that would not be possible otherwise - yet they add complexity in jOOQ's internals.
org.jooq.impl.DSL.createView(Name, Function<? super Field<?>, ? extends Name>)	- 3.14.0 - [#10156] - These methods will be removed without replacement from a future jOOQ. They offer convenience that is unidiomatic for jOOQ's DSL, without offering functionality that would not be possible otherwise - yet they add complexity in jOOQ's internals.
org.jooq.impl.DSL.createView(Table<?>, Function<? super Field<?>, ? extends Field<?>>)	- 3.14.0 - [#10156] - These methods will be removed without replacement from a future jOOQ. They offer convenience that is unidiomatic for jOOQ's DSL, without offering functionality that would not be possible otherwise - yet they add complexity in jOOQ's internals.
org.jooq.impl.DSL.createViewIfNotExists(String, Function<? super Field<?>, ? extends String>)	- 3.14.0 - [#10156] - These methods will be removed without replacement from a future jOOQ. They offer convenience that is unidiomatic for jOOQ's DSL, without offering functionality that would not be possible otherwise - yet they add complexity in jOOQ's internals.
org.jooq.impl.DSL.createViewIfNotExists(Name, Function<? super Field<?>, ? extends Name>)	- 3.14.0 - [#10156] - These methods will be removed without replacement from a future jOOQ. They offer convenience that is unidiomatic for jOOQ's DSL, without offering functionality that would not be possible otherwise - yet they add complexity in jOOQ's internals.
org.jooq.impl.DSL.createViewIfNotExists(Table<?>, Function<? super Field<?>, ? extends Field<?>>)	- 3.14.0 - [#10156] - These methods will be removed without replacement from a future jOOQ. They offer convenience that is unidiomatic for jOOQ's DSL, without offering functionality that would not be possible otherwise - yet they add complexity in jOOQ's internals.
org.jooq.impl.DSL.getDataType(Class<T>)	- 3.11.0 - [#7483] - The (indirect) use of the internal static data type registry is not recommended.
org.jooq.impl.DSL.groupConcat(Field<?>, String)	- [#7956] - 3.12.0 - Use DSL.groupConcat(Field) and GroupConcatSeparatorStep.separator(String) instead.
org.jooq.impl.DSL.mergeInto(Table<R>, Collection<? extends Field<?>>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSL.mergeInto(Table)
org.jooq.impl.DSL.mergeInto(Table<R>, Field<?>...)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSL.mergeInto(Table)
org.jooq.impl.DSL.mergeInto(Table<R>, Field<T1>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSL.mergeInto(Table)
org.jooq.impl.DSL.mergeInto(Table<R>, Field<T1>, Field<T2>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSL.mergeInto(Table)
org.jooq.impl.DSL.mergeInto(Table<R>, Field<T1>, Field<T2>, Field<T3>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSL.mergeInto(Table)
org.jooq.impl.DSL.mergeInto(Table<R>, Field<T1>, Field<T2>, Field<T3>, Field<T4>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSL.mergeInto(Table)
org.jooq.impl.DSL.mergeInto(Table<R>, Field<T1>, Field<T2>, Field<T3>, Field<T4>, Field<T5>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSL.mergeInto(Table)
org.jooq.impl.DSL.mergeInto(Table<R>, Field<T1>, Field<T2>, Field<T3>, Field<T4>, Field<T5>, Field<T6>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSL.mergeInto(Table)
org.jooq.impl.DSL.mergeInto(Table<R>, Field<T1>, Field<T2>, Field<T3>, Field<T4>, Field<T5>, Field<T6>, Field<T7>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSL.mergeInto(Table)
org.jooq.impl.DSL.mergeInto(Table<R>, Field<T1>, Field<T2>, Field<T3>, Field<T4>, Field<T5>, Field<T6>, Field<T7>, Field<T8>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSL.mergeInto(Table)
org.jooq.impl.DSL.mergeInto(Table<R>, Field<T1>, Field<T2>, Field<T3>, Field<T4>, Field<T5>, Field<T6>, Field<T7>, Field<T8>, Field<T9>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSL.mergeInto(Table)
org.jooq.impl.DSL.mergeInto(Table<R>, Field<T1>, Field<T2>, Field<T3>, Field<T4>, Field<T5>, Field<T6>, Field<T7>, Field<T8>, Field<T9>, Field<T10>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSL.mergeInto(Table)
org.jooq.impl.DSL.mergeInto(Table<R>, Field<T1>, Field<T2>, Field<T3>, Field<T4>, Field<T5>, Field<T6>, Field<T7>, Field<T8>, Field<T9>, Field<T10>, Field<T11>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSL.mergeInto(Table)
org.jooq.impl.DSL.mergeInto(Table<R>, Field<T1>, Field<T2>, Field<T3>, Field<T4>, Field<T5>, Field<T6>, Field<T7>, Field<T8>, Field<T9>, Field<T10>, Field<T11>, Field<T12>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSL.mergeInto(Table)
org.jooq.impl.DSL.mergeInto(Table<R>, Field<T1>, Field<T2>, Field<T3>, Field<T4>, Field<T5>, Field<T6>, Field<T7>, Field<T8>, Field<T9>, Field<T10>, Field<T11>, Field<T12>, Field<T13>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSL.mergeInto(Table)
org.jooq.impl.DSL.mergeInto(Table<R>, Field<T1>, Field<T2>, Field<T3>, Field<T4>, Field<T5>, Field<T6>, Field<T7>, Field<T8>, Field<T9>, Field<T10>, Field<T11>, Field<T12>, Field<T13>, Field<T14>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSL.mergeInto(Table)
org.jooq.impl.DSL.mergeInto(Table<R>, Field<T1>, Field<T2>, Field<T3>, Field<T4>, Field<T5>, Field<T6>, Field<T7>, Field<T8>, Field<T9>, Field<T10>, Field<T11>, Field<T12>, Field<T13>, Field<T14>, Field<T15>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSL.mergeInto(Table)
org.jooq.impl.DSL.mergeInto(Table<R>, Field<T1>, Field<T2>, Field<T3>, Field<T4>, Field<T5>, Field<T6>, Field<T7>, Field<T8>, Field<T9>, Field<T10>, Field<T11>, Field<T12>, Field<T13>, Field<T14>, Field<T15>, Field<T16>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSL.mergeInto(Table)
org.jooq.impl.DSL.mergeInto(Table<R>, Field<T1>, Field<T2>, Field<T3>, Field<T4>, Field<T5>, Field<T6>, Field<T7>, Field<T8>, Field<T9>, Field<T10>, Field<T11>, Field<T12>, Field<T13>, Field<T14>, Field<T15>, Field<T16>, Field<T17>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSL.mergeInto(Table)
org.jooq.impl.DSL.mergeInto(Table<R>, Field<T1>, Field<T2>, Field<T3>, Field<T4>, Field<T5>, Field<T6>, Field<T7>, Field<T8>, Field<T9>, Field<T10>, Field<T11>, Field<T12>, Field<T13>, Field<T14>, Field<T15>, Field<T16>, Field<T17>, Field<T18>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSL.mergeInto(Table)
org.jooq.impl.DSL.mergeInto(Table<R>, Field<T1>, Field<T2>, Field<T3>, Field<T4>, Field<T5>, Field<T6>, Field<T7>, Field<T8>, Field<T9>, Field<T10>, Field<T11>, Field<T12>, Field<T13>, Field<T14>, Field<T15>, Field<T16>, Field<T17>, Field<T18>, Field<T19>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSL.mergeInto(Table)
org.jooq.impl.DSL.mergeInto(Table<R>, Field<T1>, Field<T2>, Field<T3>, Field<T4>, Field<T5>, Field<T6>, Field<T7>, Field<T8>, Field<T9>, Field<T10>, Field<T11>, Field<T12>, Field<T13>, Field<T14>, Field<T15>, Field<T16>, Field<T17>, Field<T18>, Field<T19>, Field<T20>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSL.mergeInto(Table)
org.jooq.impl.DSL.mergeInto(Table<R>, Field<T1>, Field<T2>, Field<T3>, Field<T4>, Field<T5>, Field<T6>, Field<T7>, Field<T8>, Field<T9>, Field<T10>, Field<T11>, Field<T12>, Field<T13>, Field<T14>, Field<T15>, Field<T16>, Field<T17>, Field<T18>, Field<T19>, Field<T20>, Field<T21>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSL.mergeInto(Table)
org.jooq.impl.DSL.mergeInto(Table<R>, Field<T1>, Field<T2>, Field<T3>, Field<T4>, Field<T5>, Field<T6>, Field<T7>, Field<T8>, Field<T9>, Field<T10>, Field<T11>, Field<T12>, Field<T13>, Field<T14>, Field<T15>, Field<T16>, Field<T17>, Field<T18>, Field<T19>, Field<T20>, Field<T21>, Field<T22>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSL.mergeInto(Table)
org.jooq.impl.DSL.nullSafe(Field<?>...)	- [#11092] - 3.15.0 - This method will be removed without public replacement.
org.jooq.impl.DSL.nullSafe(Field<?>[], DataType<?>)	- [#11092] - 3.15.0 - This method will be removed without public replacement.
org.jooq.impl.DSL.nullSafe(Field<T>)	- [#11092] - 3.15.0 - This method will be removed without public replacement.
org.jooq.impl.DSL.nullSafe(Field<T>, DataType<?>)	- [#11092] - 3.15.0 - This method will be removed without public replacement.
org.jooq.impl.DSL.nullSafeDataType(Field<T>)	- [#11092] - 3.15.0 - This method will be removed without public replacement.
org.jooq.impl.DSL.nullSafeList(Field<?>...)	- [#11092] - 3.15.0 - This method will be removed without public replacement.
org.jooq.impl.DSL.nullSafeList(Field<?>[], DataType<?>)	- [#11092] - 3.15.0 - This method will be removed without public replacement.
org.jooq.impl.DSL.rowField(Row1<T1>)	- [#11812] - 3.15.0 - Use Row1 as a SelectField directly, instead.
org.jooq.impl.DSL.rowField(Row10<T1, T2, T3, T4, T5, T6, T7, T8, T9, T10>)	- [#11812] - 3.15.0 - Use Row10 as a SelectField directly, instead.
org.jooq.impl.DSL.rowField(Row11<T1, T2, T3, T4, T5, T6, T7, T8, T9, T10, T11>)	- [#11812] - 3.15.0 - Use Row11 as a SelectField directly, instead.
org.jooq.impl.DSL.rowField(Row12<T1, T2, T3, T4, T5, T6, T7, T8, T9, T10, T11, T12>)	- [#11812] - 3.15.0 - Use Row12 as a SelectField directly, instead.
org.jooq.impl.DSL.rowField(Row13<T1, T2, T3, T4, T5, T6, T7, T8, T9, T10, T11, T12, T13>)	- [#11812] - 3.15.0 - Use Row13 as a SelectField directly, instead.
org.jooq.impl.DSL.rowField(Row14<T1, T2, T3, T4, T5, T6, T7, T8, T9, T10, T11, T12, T13, T14>)	- [#11812] - 3.15.0 - Use Row14 as a SelectField directly, instead.
org.jooq.impl.DSL.rowField(Row15<T1, T2, T3, T4, T5, T6, T7, T8, T9, T10, T11, T12, T13, T14, T15>)	- [#11812] - 3.15.0 - Use Row15 as a SelectField directly, instead.
org.jooq.impl.DSL.rowField(Row16<T1, T2, T3, T4, T5, T6, T7, T8, T9, T10, T11, T12, T13, T14, T15, T16>)	- [#11812] - 3.15.0 - Use Row16 as a SelectField directly, instead.
org.jooq.impl.DSL.rowField(Row17<T1, T2, T3, T4, T5, T6, T7, T8, T9, T10, T11, T12, T13, T14, T15, T16, T17>)	- [#11812] - 3.15.0 - Use Row17 as a SelectField directly, instead.
org.jooq.impl.DSL.rowField(Row18<T1, T2, T3, T4, T5, T6, T7, T8, T9, T10, T11, T12, T13, T14, T15, T16, T17, T18>)	- [#11812] - 3.15.0 - Use Row18 as a SelectField directly, instead.
org.jooq.impl.DSL.rowField(Row19<T1, T2, T3, T4, T5, T6, T7, T8, T9, T10, T11, T12, T13, T14, T15, T16, T17, T18, T19>)	- [#11812] - 3.15.0 - Use Row19 as a SelectField directly, instead.
org.jooq.impl.DSL.rowField(Row2<T1, T2>)	- [#11812] - 3.15.0 - Use Row2 as a SelectField directly, instead.
org.jooq.impl.DSL.rowField(Row20<T1, T2, T3, T4, T5, T6, T7, T8, T9, T10, T11, T12, T13, T14, T15, T16, T17, T18, T19, T20>)	- [#11812] - 3.15.0 - Use Row20 as a SelectField directly, instead.
org.jooq.impl.DSL.rowField(Row21<T1, T2, T3, T4, T5, T6, T7, T8, T9, T10, T11, T12, T13, T14, T15, T16, T17, T18, T19, T20, T21>)	- [#11812] - 3.15.0 - Use Row21 as a SelectField directly, instead.
org.jooq.impl.DSL.rowField(Row22<T1, T2, T3, T4, T5, T6, T7, T8, T9, T10, T11, T12, T13, T14, T15, T16, T17, T18, T19, T20, T21, T22>)	- [#11812] - 3.15.0 - Use Row22 as a SelectField directly, instead.
org.jooq.impl.DSL.rowField(Row3<T1, T2, T3>)	- [#11812] - 3.15.0 - Use Row3 as a SelectField directly, instead.
org.jooq.impl.DSL.rowField(Row4<T1, T2, T3, T4>)	- [#11812] - 3.15.0 - Use Row4 as a SelectField directly, instead.
org.jooq.impl.DSL.rowField(Row5<T1, T2, T3, T4, T5>)	- [#11812] - 3.15.0 - Use Row5 as a SelectField directly, instead.
org.jooq.impl.DSL.rowField(Row6<T1, T2, T3, T4, T5, T6>)	- [#11812] - 3.15.0 - Use Row6 as a SelectField directly, instead.
org.jooq.impl.DSL.rowField(Row7<T1, T2, T3, T4, T5, T6, T7>)	- [#11812] - 3.15.0 - Use Row7 as a SelectField directly, instead.
org.jooq.impl.DSL.rowField(Row8<T1, T2, T3, T4, T5, T6, T7, T8>)	- [#11812] - 3.15.0 - Use Row8 as a SelectField directly, instead.
org.jooq.impl.DSL.rowField(Row9<T1, T2, T3, T4, T5, T6, T7, T8, T9>)	- [#11812] - 3.15.0 - Use Row9 as a SelectField directly, instead.
org.jooq.impl.DSL.rowField(RowN)	- [#11812] - 3.15.0 - Use RowN as a SelectField directly, instead.
org.jooq.impl.DSL.sequence(String)	- 3.10 - [#6162] - Use DSL.sequence(Name) instead.
org.jooq.impl.DSL.sequence(String, Class<T>)	- 3.10 - [#6162] - Use DSL.sequence(Name, Class) instead.
org.jooq.impl.DSL.sequence(String, DataType<T>)	- 3.10 - [#6162] - Use DSL.sequence(Name, DataType) instead.
org.jooq.impl.DSL.with(String, Function<? super Field<?>, ? extends String>)	- 3.14.0 - [#10156] - These methods will be removed without replacement from a future jOOQ. They offer convenience that is unidiomatic for jOOQ's DSL, without offering functionality that would not be possible otherwise - yet they add complexity in jOOQ's internals.
org.jooq.impl.DSL.withRecursive(String, Function<? super Field<?>, ? extends String>)	- 3.14.0 - [#10156] - These methods will be removed without replacement from a future jOOQ. They offer convenience that is unidiomatic for jOOQ's DSL, without offering functionality that would not be possible otherwise - yet they add complexity in jOOQ's internals.
org.jooq.impl.Internal.createForeignKey(UniqueKey<U>, Table<R>, String, TableField<R, ?>...)	- 3.14.0 - [#9404] - Please re-generate your code.
org.jooq.impl.Internal.createForeignKey(UniqueKey<U>, Table<R>, String, TableField<R, ?>[], boolean)	- 3.14.0 - [#9404] - Please re-generate your code.
org.jooq.impl.Internal.createIndex(String, Table<?>, OrderField<?>[], boolean)	- 3.14.0 - [#9404] - Please re-generate your code.
org.jooq.impl.Internal.createUniqueKey(Table<R>, String, TableField<R, ?>...)	- 3.14.0 - [#9404] - Please re-generate your code.
org.jooq.impl.Internal.createUniqueKey(Table<R>, String, TableField<R, ?>[], boolean)	- 3.14.0 - [#9404] - Please re-generate your code.
org.jooq.impl.Internal.fields(TableField<R, ER>)	- [#11058] - 3.14.5 - Please re-generate your code.
org.jooq.impl.Internal.fieldsRow(TableField<R, ER>)	- [#12238] - 3.16.0 - Please re-generate your code.
org.jooq.impl.QOM.NotYetImplementedException	- [#12425] - 3.16.0 - Missing implementations should be added as soon as possible!
org.jooq.InsertFinalStep	- [#11329] - 3.15.0 - This type will be removed in the future. Do not reference it directly
org.jooq.LoaderCSVStep.fieldsFromSource()	- 3.14.0 - [#10010] - Use LoaderCSVStep.fieldsCorresponding() instead.
org.jooq.LoaderJSONStep.fieldsFromSource()	- 3.14.0 - [#10010] - Use LoaderJSONStep.fieldsCorresponding() instead.
org.jooq.LoaderListenerStep.onRow(LoaderRowListener)	- 3.14.0 - [#4941] - Use LoaderListenerStep.onRowEnd(LoaderRowListener) instead.
org.jooq.LoaderRowsStep.fieldsFromSource()	- 3.14.0 - [#10010] - Use LoaderRowsStep.fieldsCorresponding() instead.
org.jooq.MergeFinalStep	- [#11329] - 3.15.0 - This type will be removed in the future. Do not reference it directly
org.jooq.MergeKeyStep1	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeKeyStep1.key(Collection<? extends Field<?>>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeKeyStep1.key(Field<?>...)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeKeyStep10	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeKeyStep10.key(Collection<? extends Field<?>>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeKeyStep10.key(Field<?>...)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeKeyStep11	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeKeyStep11.key(Collection<? extends Field<?>>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeKeyStep11.key(Field<?>...)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeKeyStep12	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeKeyStep12.key(Collection<? extends Field<?>>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeKeyStep12.key(Field<?>...)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeKeyStep13	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeKeyStep13.key(Collection<? extends Field<?>>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeKeyStep13.key(Field<?>...)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeKeyStep14	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeKeyStep14.key(Collection<? extends Field<?>>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeKeyStep14.key(Field<?>...)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeKeyStep15	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeKeyStep15.key(Collection<? extends Field<?>>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeKeyStep15.key(Field<?>...)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeKeyStep16	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeKeyStep16.key(Collection<? extends Field<?>>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeKeyStep16.key(Field<?>...)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeKeyStep17	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeKeyStep17.key(Collection<? extends Field<?>>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeKeyStep17.key(Field<?>...)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeKeyStep18	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeKeyStep18.key(Collection<? extends Field<?>>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeKeyStep18.key(Field<?>...)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeKeyStep19	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeKeyStep19.key(Collection<? extends Field<?>>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeKeyStep19.key(Field<?>...)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeKeyStep2	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeKeyStep2.key(Collection<? extends Field<?>>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeKeyStep2.key(Field<?>...)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeKeyStep20	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeKeyStep20.key(Collection<? extends Field<?>>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeKeyStep20.key(Field<?>...)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeKeyStep21	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeKeyStep21.key(Collection<? extends Field<?>>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeKeyStep21.key(Field<?>...)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeKeyStep22	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeKeyStep22.key(Collection<? extends Field<?>>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeKeyStep22.key(Field<?>...)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeKeyStep3	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeKeyStep3.key(Collection<? extends Field<?>>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeKeyStep3.key(Field<?>...)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeKeyStep4	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeKeyStep4.key(Collection<? extends Field<?>>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeKeyStep4.key(Field<?>...)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeKeyStep5	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeKeyStep5.key(Collection<? extends Field<?>>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeKeyStep5.key(Field<?>...)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeKeyStep6	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeKeyStep6.key(Collection<? extends Field<?>>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeKeyStep6.key(Field<?>...)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeKeyStep7	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeKeyStep7.key(Collection<? extends Field<?>>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeKeyStep7.key(Field<?>...)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeKeyStep8	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeKeyStep8.key(Collection<? extends Field<?>>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeKeyStep8.key(Field<?>...)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeKeyStep9	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeKeyStep9.key(Collection<? extends Field<?>>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeKeyStep9.key(Field<?>...)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeUsingStep.columns(Collection<? extends Field<?>>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeUsingStep.columns(Field<?>...)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeUsingStep.columns(Field<T1>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeUsingStep.columns(Field<T1>, Field<T2>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeUsingStep.columns(Field<T1>, Field<T2>, Field<T3>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeUsingStep.columns(Field<T1>, Field<T2>, Field<T3>, Field<T4>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeUsingStep.columns(Field<T1>, Field<T2>, Field<T3>, Field<T4>, Field<T5>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeUsingStep.columns(Field<T1>, Field<T2>, Field<T3>, Field<T4>, Field<T5>, Field<T6>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeUsingStep.columns(Field<T1>, Field<T2>, Field<T3>, Field<T4>, Field<T5>, Field<T6>, Field<T7>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeUsingStep.columns(Field<T1>, Field<T2>, Field<T3>, Field<T4>, Field<T5>, Field<T6>, Field<T7>, Field<T8>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeUsingStep.columns(Field<T1>, Field<T2>, Field<T3>, Field<T4>, Field<T5>, Field<T6>, Field<T7>, Field<T8>, Field<T9>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeUsingStep.columns(Field<T1>, Field<T2>, Field<T3>, Field<T4>, Field<T5>, Field<T6>, Field<T7>, Field<T8>, Field<T9>, Field<T10>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeUsingStep.columns(Field<T1>, Field<T2>, Field<T3>, Field<T4>, Field<T5>, Field<T6>, Field<T7>, Field<T8>, Field<T9>, Field<T10>, Field<T11>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeUsingStep.columns(Field<T1>, Field<T2>, Field<T3>, Field<T4>, Field<T5>, Field<T6>, Field<T7>, Field<T8>, Field<T9>, Field<T10>, Field<T11>, Field<T12>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeUsingStep.columns(Field<T1>, Field<T2>, Field<T3>, Field<T4>, Field<T5>, Field<T6>, Field<T7>, Field<T8>, Field<T9>, Field<T10>, Field<T11>, Field<T12>, Field<T13>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeUsingStep.columns(Field<T1>, Field<T2>, Field<T3>, Field<T4>, Field<T5>, Field<T6>, Field<T7>, Field<T8>, Field<T9>, Field<T10>, Field<T11>, Field<T12>, Field<T13>, Field<T14>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeUsingStep.columns(Field<T1>, Field<T2>, Field<T3>, Field<T4>, Field<T5>, Field<T6>, Field<T7>, Field<T8>, Field<T9>, Field<T10>, Field<T11>, Field<T12>, Field<T13>, Field<T14>, Field<T15>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeUsingStep.columns(Field<T1>, Field<T2>, Field<T3>, Field<T4>, Field<T5>, Field<T6>, Field<T7>, Field<T8>, Field<T9>, Field<T10>, Field<T11>, Field<T12>, Field<T13>, Field<T14>, Field<T15>, Field<T16>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeUsingStep.columns(Field<T1>, Field<T2>, Field<T3>, Field<T4>, Field<T5>, Field<T6>, Field<T7>, Field<T8>, Field<T9>, Field<T10>, Field<T11>, Field<T12>, Field<T13>, Field<T14>, Field<T15>, Field<T16>, Field<T17>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeUsingStep.columns(Field<T1>, Field<T2>, Field<T3>, Field<T4>, Field<T5>, Field<T6>, Field<T7>, Field<T8>, Field<T9>, Field<T10>, Field<T11>, Field<T12>, Field<T13>, Field<T14>, Field<T15>, Field<T16>, Field<T17>, Field<T18>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeUsingStep.columns(Field<T1>, Field<T2>, Field<T3>, Field<T4>, Field<T5>, Field<T6>, Field<T7>, Field<T8>, Field<T9>, Field<T10>, Field<T11>, Field<T12>, Field<T13>, Field<T14>, Field<T15>, Field<T16>, Field<T17>, Field<T18>, Field<T19>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeUsingStep.columns(Field<T1>, Field<T2>, Field<T3>, Field<T4>, Field<T5>, Field<T6>, Field<T7>, Field<T8>, Field<T9>, Field<T10>, Field<T11>, Field<T12>, Field<T13>, Field<T14>, Field<T15>, Field<T16>, Field<T17>, Field<T18>, Field<T19>, Field<T20>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeUsingStep.columns(Field<T1>, Field<T2>, Field<T3>, Field<T4>, Field<T5>, Field<T6>, Field<T7>, Field<T8>, Field<T9>, Field<T10>, Field<T11>, Field<T12>, Field<T13>, Field<T14>, Field<T15>, Field<T16>, Field<T17>, Field<T18>, Field<T19>, Field<T20>, Field<T21>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeUsingStep.columns(Field<T1>, Field<T2>, Field<T3>, Field<T4>, Field<T5>, Field<T6>, Field<T7>, Field<T8>, Field<T9>, Field<T10>, Field<T11>, Field<T12>, Field<T13>, Field<T14>, Field<T15>, Field<T16>, Field<T17>, Field<T18>, Field<T19>, Field<T20>, Field<T21>, Field<T22>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeValuesStep1	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeValuesStep1.select(Select<? extends Record1<T1>>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeValuesStep1.values(Collection<?>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeValuesStep1.values(Field<T1>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeValuesStep1.values(T1)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeValuesStep10	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeValuesStep10.select(Select<? extends Record10<T1, T2, T3, T4, T5, T6, T7, T8, T9, T10>>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeValuesStep10.values(Collection<?>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeValuesStep10.values(Field<T1>, Field<T2>, Field<T3>, Field<T4>, Field<T5>, Field<T6>, Field<T7>, Field<T8>, Field<T9>, Field<T10>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeValuesStep10.values(T1, T2, T3, T4, T5, T6, T7, T8, T9, T10)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeValuesStep11	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeValuesStep11.select(Select<? extends Record11<T1, T2, T3, T4, T5, T6, T7, T8, T9, T10, T11>>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeValuesStep11.values(Collection<?>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeValuesStep11.values(Field<T1>, Field<T2>, Field<T3>, Field<T4>, Field<T5>, Field<T6>, Field<T7>, Field<T8>, Field<T9>, Field<T10>, Field<T11>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeValuesStep11.values(T1, T2, T3, T4, T5, T6, T7, T8, T9, T10, T11)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeValuesStep12	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeValuesStep12.select(Select<? extends Record12<T1, T2, T3, T4, T5, T6, T7, T8, T9, T10, T11, T12>>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeValuesStep12.values(Collection<?>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeValuesStep12.values(Field<T1>, Field<T2>, Field<T3>, Field<T4>, Field<T5>, Field<T6>, Field<T7>, Field<T8>, Field<T9>, Field<T10>, Field<T11>, Field<T12>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeValuesStep12.values(T1, T2, T3, T4, T5, T6, T7, T8, T9, T10, T11, T12)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeValuesStep13	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeValuesStep13.select(Select<? extends Record13<T1, T2, T3, T4, T5, T6, T7, T8, T9, T10, T11, T12, T13>>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeValuesStep13.values(Collection<?>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeValuesStep13.values(Field<T1>, Field<T2>, Field<T3>, Field<T4>, Field<T5>, Field<T6>, Field<T7>, Field<T8>, Field<T9>, Field<T10>, Field<T11>, Field<T12>, Field<T13>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeValuesStep13.values(T1, T2, T3, T4, T5, T6, T7, T8, T9, T10, T11, T12, T13)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeValuesStep14	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeValuesStep14.select(Select<? extends Record14<T1, T2, T3, T4, T5, T6, T7, T8, T9, T10, T11, T12, T13, T14>>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeValuesStep14.values(Collection<?>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeValuesStep14.values(Field<T1>, Field<T2>, Field<T3>, Field<T4>, Field<T5>, Field<T6>, Field<T7>, Field<T8>, Field<T9>, Field<T10>, Field<T11>, Field<T12>, Field<T13>, Field<T14>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeValuesStep14.values(T1, T2, T3, T4, T5, T6, T7, T8, T9, T10, T11, T12, T13, T14)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeValuesStep15	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeValuesStep15.select(Select<? extends Record15<T1, T2, T3, T4, T5, T6, T7, T8, T9, T10, T11, T12, T13, T14, T15>>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeValuesStep15.values(Collection<?>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeValuesStep15.values(Field<T1>, Field<T2>, Field<T3>, Field<T4>, Field<T5>, Field<T6>, Field<T7>, Field<T8>, Field<T9>, Field<T10>, Field<T11>, Field<T12>, Field<T13>, Field<T14>, Field<T15>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeValuesStep15.values(T1, T2, T3, T4, T5, T6, T7, T8, T9, T10, T11, T12, T13, T14, T15)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeValuesStep16	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeValuesStep16.select(Select<? extends Record16<T1, T2, T3, T4, T5, T6, T7, T8, T9, T10, T11, T12, T13, T14, T15, T16>>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeValuesStep16.values(Collection<?>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeValuesStep16.values(Field<T1>, Field<T2>, Field<T3>, Field<T4>, Field<T5>, Field<T6>, Field<T7>, Field<T8>, Field<T9>, Field<T10>, Field<T11>, Field<T12>, Field<T13>, Field<T14>, Field<T15>, Field<T16>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeValuesStep16.values(T1, T2, T3, T4, T5, T6, T7, T8, T9, T10, T11, T12, T13, T14, T15, T16)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeValuesStep17	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeValuesStep17.select(Select<? extends Record17<T1, T2, T3, T4, T5, T6, T7, T8, T9, T10, T11, T12, T13, T14, T15, T16, T17>>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeValuesStep17.values(Collection<?>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeValuesStep17.values(Field<T1>, Field<T2>, Field<T3>, Field<T4>, Field<T5>, Field<T6>, Field<T7>, Field<T8>, Field<T9>, Field<T10>, Field<T11>, Field<T12>, Field<T13>, Field<T14>, Field<T15>, Field<T16>, Field<T17>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeValuesStep17.values(T1, T2, T3, T4, T5, T6, T7, T8, T9, T10, T11, T12, T13, T14, T15, T16, T17)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeValuesStep18	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeValuesStep18.select(Select<? extends Record18<T1, T2, T3, T4, T5, T6, T7, T8, T9, T10, T11, T12, T13, T14, T15, T16, T17, T18>>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeValuesStep18.values(Collection<?>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeValuesStep18.values(Field<T1>, Field<T2>, Field<T3>, Field<T4>, Field<T5>, Field<T6>, Field<T7>, Field<T8>, Field<T9>, Field<T10>, Field<T11>, Field<T12>, Field<T13>, Field<T14>, Field<T15>, Field<T16>, Field<T17>, Field<T18>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeValuesStep18.values(T1, T2, T3, T4, T5, T6, T7, T8, T9, T10, T11, T12, T13, T14, T15, T16, T17, T18)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeValuesStep19	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeValuesStep19.select(Select<? extends Record19<T1, T2, T3, T4, T5, T6, T7, T8, T9, T10, T11, T12, T13, T14, T15, T16, T17, T18, T19>>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeValuesStep19.values(Collection<?>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeValuesStep19.values(Field<T1>, Field<T2>, Field<T3>, Field<T4>, Field<T5>, Field<T6>, Field<T7>, Field<T8>, Field<T9>, Field<T10>, Field<T11>, Field<T12>, Field<T13>, Field<T14>, Field<T15>, Field<T16>, Field<T17>, Field<T18>, Field<T19>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeValuesStep19.values(T1, T2, T3, T4, T5, T6, T7, T8, T9, T10, T11, T12, T13, T14, T15, T16, T17, T18, T19)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeValuesStep2	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeValuesStep2.select(Select<? extends Record2<T1, T2>>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeValuesStep2.values(Collection<?>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeValuesStep2.values(Field<T1>, Field<T2>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeValuesStep2.values(T1, T2)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeValuesStep20	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeValuesStep20.select(Select<? extends Record20<T1, T2, T3, T4, T5, T6, T7, T8, T9, T10, T11, T12, T13, T14, T15, T16, T17, T18, T19, T20>>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeValuesStep20.values(Collection<?>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeValuesStep20.values(Field<T1>, Field<T2>, Field<T3>, Field<T4>, Field<T5>, Field<T6>, Field<T7>, Field<T8>, Field<T9>, Field<T10>, Field<T11>, Field<T12>, Field<T13>, Field<T14>, Field<T15>, Field<T16>, Field<T17>, Field<T18>, Field<T19>, Field<T20>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeValuesStep20.values(T1, T2, T3, T4, T5, T6, T7, T8, T9, T10, T11, T12, T13, T14, T15, T16, T17, T18, T19, T20)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeValuesStep21	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeValuesStep21.select(Select<? extends Record21<T1, T2, T3, T4, T5, T6, T7, T8, T9, T10, T11, T12, T13, T14, T15, T16, T17, T18, T19, T20, T21>>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeValuesStep21.values(Collection<?>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeValuesStep21.values(Field<T1>, Field<T2>, Field<T3>, Field<T4>, Field<T5>, Field<T6>, Field<T7>, Field<T8>, Field<T9>, Field<T10>, Field<T11>, Field<T12>, Field<T13>, Field<T14>, Field<T15>, Field<T16>, Field<T17>, Field<T18>, Field<T19>, Field<T20>, Field<T21>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeValuesStep21.values(T1, T2, T3, T4, T5, T6, T7, T8, T9, T10, T11, T12, T13, T14, T15, T16, T17, T18, T19, T20, T21)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeValuesStep22	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeValuesStep22.select(Select<? extends Record22<T1, T2, T3, T4, T5, T6, T7, T8, T9, T10, T11, T12, T13, T14, T15, T16, T17, T18, T19, T20, T21, T22>>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeValuesStep22.values(Collection<?>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeValuesStep22.values(Field<T1>, Field<T2>, Field<T3>, Field<T4>, Field<T5>, Field<T6>, Field<T7>, Field<T8>, Field<T9>, Field<T10>, Field<T11>, Field<T12>, Field<T13>, Field<T14>, Field<T15>, Field<T16>, Field<T17>, Field<T18>, Field<T19>, Field<T20>, Field<T21>, Field<T22>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeValuesStep22.values(T1, T2, T3, T4, T5, T6, T7, T8, T9, T10, T11, T12, T13, T14, T15, T16, T17, T18, T19, T20, T21, T22)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeValuesStep3	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeValuesStep3.select(Select<? extends Record3<T1, T2, T3>>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeValuesStep3.values(Collection<?>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeValuesStep3.values(Field<T1>, Field<T2>, Field<T3>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeValuesStep3.values(T1, T2, T3)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeValuesStep4	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeValuesStep4.select(Select<? extends Record4<T1, T2, T3, T4>>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeValuesStep4.values(Collection<?>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeValuesStep4.values(Field<T1>, Field<T2>, Field<T3>, Field<T4>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeValuesStep4.values(T1, T2, T3, T4)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeValuesStep5	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeValuesStep5.select(Select<? extends Record5<T1, T2, T3, T4, T5>>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeValuesStep5.values(Collection<?>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeValuesStep5.values(Field<T1>, Field<T2>, Field<T3>, Field<T4>, Field<T5>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeValuesStep5.values(T1, T2, T3, T4, T5)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeValuesStep6	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeValuesStep6.select(Select<? extends Record6<T1, T2, T3, T4, T5, T6>>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeValuesStep6.values(Collection<?>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeValuesStep6.values(Field<T1>, Field<T2>, Field<T3>, Field<T4>, Field<T5>, Field<T6>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeValuesStep6.values(T1, T2, T3, T4, T5, T6)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeValuesStep7	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeValuesStep7.select(Select<? extends Record7<T1, T2, T3, T4, T5, T6, T7>>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeValuesStep7.values(Collection<?>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeValuesStep7.values(Field<T1>, Field<T2>, Field<T3>, Field<T4>, Field<T5>, Field<T6>, Field<T7>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeValuesStep7.values(T1, T2, T3, T4, T5, T6, T7)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeValuesStep8	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeValuesStep8.select(Select<? extends Record8<T1, T2, T3, T4, T5, T6, T7, T8>>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeValuesStep8.values(Collection<?>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeValuesStep8.values(Field<T1>, Field<T2>, Field<T3>, Field<T4>, Field<T5>, Field<T6>, Field<T7>, Field<T8>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeValuesStep8.values(T1, T2, T3, T4, T5, T6, T7, T8)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeValuesStep9	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeValuesStep9.select(Select<? extends Record9<T1, T2, T3, T4, T5, T6, T7, T8, T9>>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeValuesStep9.values(Collection<?>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeValuesStep9.values(Field<T1>, Field<T2>, Field<T3>, Field<T4>, Field<T5>, Field<T6>, Field<T7>, Field<T8>, Field<T9>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeValuesStep9.values(T1, T2, T3, T4, T5, T6, T7, T8, T9)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.Name.fields(BiFunction<? super Field<?>, ? super Integer, ? extends String>)	- 3.14.0 - [#10156] - These methods will be removed without replacement from a future jOOQ. They offer convenience that is unidiomatic for jOOQ's DSL, without offering functionality that would not be possible otherwise - yet they add complexity in jOOQ's internals.
org.jooq.Name.fields(Function<? super Field<?>, ? extends String>)	- 3.14.0 - [#10156] - These methods will be removed without replacement from a future jOOQ. They offer convenience that is unidiomatic for jOOQ's DSL, without offering functionality that would not be possible otherwise - yet they add complexity in jOOQ's internals.
org.jooq.Param.setConverted(Object)	- 3.8.0 - [#4991] In jOOQ 4.0, Param will be made immutable. Modifying Param values is strongly discouraged.
org.jooq.Param.setInline(boolean)	- 3.8.0 - [#4991] In jOOQ 4.0, Param will be made immutable. Modifying Param values is strongly discouraged.
org.jooq.Param.setValue(T)	- 3.8.0 - [#4991] In jOOQ 4.0, Param will be made immutable. Modifying Param values is strongly discouraged.
org.jooq.PivotForStep.on(Field<T>)	- 3.12.0 - [#8163] - Use PivotForStep.for_(Field) instead.
org.jooq.Queries.stream()	- 3.10 - [#6143] - Use Queries.queryStream() instead.
org.jooq.RecordHandler	- 3.15.0 - [#11902] - Use Iterable.forEach(Consumer) based methods, instead.
org.jooq.Result.intern(int...)	- 3.10 - [#6254] - This functionality is no longer supported and will be removed in 4.0
org.jooq.Result.intern(String...)	- 3.10 - [#6254] - This functionality is no longer supported and will be removed in 4.0
org.jooq.Result.intern(Field<?>...)	- 3.10 - [#6254] - This functionality is no longer supported and will be removed in 4.0
org.jooq.Result.intern(Name...)	- 3.10 - [#6254] - This functionality is no longer supported and will be removed in 4.0
org.jooq.Result.into(H)	- 3.15.0 - [#11902] - Use Iterable.forEach(Consumer) based methods, instead.
org.jooq.ResultQuery.fetchInto(H)	- 3.15.0 - [#11902] - Use Iterable.forEach(Consumer) based methods, instead.
org.jooq.ResultQuery.intern(int...)	- 3.10 - [#6254] - This functionality is no longer supported and will be removed in 4.0
org.jooq.ResultQuery.intern(String...)	- 3.10 - [#6254] - This functionality is no longer supported and will be removed in 4.0
org.jooq.ResultQuery.intern(Field<?>...)	- 3.10 - [#6254] - This functionality is no longer supported and will be removed in 4.0
org.jooq.ResultQuery.intern(Name...)	- 3.10 - [#6254] - This functionality is no longer supported and will be removed in 4.0
org.jooq.RevokeFinalStep	- [#11329] - 3.15.0 - This type will be removed in the future. Do not reference it directly Referencing XYZ*Step types directly from client code It is usually not recommended to reference any XYZ*Step types directly from client code, or assign them to local variables. When writing dynamic SQL, creating a statement's components dynamically, and passing them to the DSL API statically is usually a better choice. See the manual's section about dynamic SQL for details: https://www.jooq.org/doc/latest/manual/sql-building/dynamic-sql. Drawbacks of referencing the XYZ*Step types directly: They're operating on mutable implementations (as of jOOQ 3.x) They're less composable and not easy to get right when dynamic SQL gets complex They're less readable They might have binary incompatible changes between minor releases
org.jooq.SchemaMapping	- 2.0.5 - Use runtime configuration Settings instead
org.jooq.SelectQuery.setForUpdateNoWait()	[#5218] - 3.14.0 - Use SelectQuery.setForLockModeNoWait()
org.jooq.SelectQuery.setForUpdateOf(Collection<? extends Field<?>>)	[#5218] - 3.14.0 - Use SelectQuery.setForLockModeOf(Collection)
org.jooq.SelectQuery.setForUpdateOf(Field<?>...)	[#5218] - 3.14.0 - Use SelectQuery.setForLockModeOf(Field...)
org.jooq.SelectQuery.setForUpdateOf(Table<?>...)	[#5218] - 3.14.0 - Use SelectQuery.setForLockModeOf(Table...)
org.jooq.SelectQuery.setForUpdateSkipLocked()	[#5218] - 3.14.0 - Use SelectQuery.setForLockModeSkipLocked()
org.jooq.SelectQuery.setForUpdateWait(int)	[#5218] - 3.14.0 - Use SelectQuery.setForLockModeWait(int)
org.jooq.SQLDialect.CUBRID	- [#9403] - 3.13.0 - This dialect is hardly used by anyone with jOOQ or without jOOQ and will be removed in the near future.
org.jooq.SQLDialect.IGNITE	- [#12465] - 3.16.0 - This dialect is hardly used by anyone with jOOQ or without jOOQ and will be removed in the near future. If you're actively using this dialect, please get in touch for extended support: https://github.com/jOOQ/jOOQ/issues/12465
org.jooq.SQLDialect.INGRES	- [#11515] - 3.15.0 - This dialect is hardly used by anyone with jOOQ or without jOOQ and will be removed in the near future. If you're actively using this dialect, please get in touch for extended support: https://github.com/jOOQ/jOOQ/issues/11515
org.jooq.SQLDialect.ORACLE10G	- [#11797] - 3.15.0 - This dialect is no longer supported. If you continue to require support for Oracle 10g, please get in touch here: https://github.com/jOOQ/jOOQ/issues/11797
org.jooq.SQLDialect.supports(Collection<SQLDialect>)	- [#9882] - 3.14.0 - Use SQLDialect.supportedBy(SQLDialect...) instead
org.jooq.Table.as(String, BiFunction<? super Field<?>, ? super Integer, ? extends String>)	- 3.14.0 - [#10156] - These methods will be removed without replacement from a future jOOQ. They offer convenience that is unidiomatic for jOOQ's DSL, without offering functionality that would not be possible otherwise - yet they add complexity in jOOQ's internals.
org.jooq.Table.as(String, Function<? super Field<?>, ? extends String>)	- 3.14.0 - [#10156] - These methods will be removed without replacement from a future jOOQ. They offer convenience that is unidiomatic for jOOQ's DSL, without offering functionality that would not be possible otherwise - yet they add complexity in jOOQ's internals.
org.jooq.Table.as(Name, BiFunction<? super Field<?>, ? super Integer, ? extends Name>)	- 3.14.0 - [#10156] - These methods will be removed without replacement from a future jOOQ. They offer convenience that is unidiomatic for jOOQ's DSL, without offering functionality that would not be possible otherwise - yet they add complexity in jOOQ's internals.
org.jooq.Table.as(Name, Function<? super Field<?>, ? extends Name>)	- 3.14.0 - [#10156] - These methods will be removed without replacement from a future jOOQ. They offer convenience that is unidiomatic for jOOQ's DSL, without offering functionality that would not be possible otherwise - yet they add complexity in jOOQ's internals.
org.jooq.Table.as(Table<?>, BiFunction<? super Field<?>, ? super Integer, ? extends Field<?>>)	- 3.14.0 - [#10156] - These methods will be removed without replacement from a future jOOQ. They offer convenience that is unidiomatic for jOOQ's DSL, without offering functionality that would not be possible otherwise - yet they add complexity in jOOQ's internals.
org.jooq.Table.as(Table<?>, Function<? super Field<?>, ? extends Field<?>>)	- 3.14.0 - [#10156] - These methods will be removed without replacement from a future jOOQ. They offer convenience that is unidiomatic for jOOQ's DSL, without offering functionality that would not be possible otherwise - yet they add complexity in jOOQ's internals.
org.jooq.TableLike.asTable(String, BiFunction<? super Field<?>, ? super Integer, ? extends String>)	- 3.14.0 - [#10156] - These methods will be removed without replacement from a future jOOQ. They offer convenience that is unidiomatic for jOOQ's DSL, without offering functionality that would not be possible otherwise - yet they add complexity in jOOQ's internals.
org.jooq.TableLike.asTable(String, Function<? super Field<?>, ? extends String>)	- 3.14.0 - [#10156] - These methods will be removed without replacement from a future jOOQ. They offer convenience that is unidiomatic for jOOQ's DSL, without offering functionality that would not be possible otherwise - yet they add complexity in jOOQ's internals.
org.jooq.tools.Convert	- 3.15.0 - [#11898] This class will be removed in the future. Do not reuse. Data type conversion happens using internal Converter implementations, or ConverterProvider provided ones, or implementations attached to fields via generated code, or via Field.convert(Converter), or DataType.asConvertedDataType(Converter).
org.jooq.TruncateFinalStep	- [#11329] - 3.15.0 - This type will be removed in the future. Do not reference it directly Referencing XYZ*Step types directly from client code It is usually not recommended to reference any XYZ*Step types directly from client code, or assign them to local variables. When writing dynamic SQL, creating a statement's components dynamically, and passing them to the DSL API statically is usually a better choice. See the manual's section about dynamic SQL for details: https://www.jooq.org/doc/latest/manual/sql-building/dynamic-sql. Drawbacks of referencing the XYZ*Step types directly: They're operating on mutable implementations (as of jOOQ 3.x) They're less composable and not easy to get right when dynamic SQL gets complex They're less readable They might have binary incompatible changes between minor releases
org.jooq.UpdateFinalStep	- [#11329] - 3.15.0 - This type will be removed in the future. Do not reference it directly
org.jooq.util.access.AccessDataType	- 3.11.0 - [#7375] - This type is part of jOOQ's internal API. Do not reference this type directly from client code. Referencing this type before the SQLDataType class has been initialised may lead to deadlocks! See https://github.com/jOOQ/jOOQ/issues/3777 for details. Use the corresponding SQLDataType instead.
org.jooq.util.access.AccessDSL	- 3.15.0 - [#10796] - This class will be removed, soon, no more vendor specific DSL API will be added.
org.jooq.util.ase.ASEDataType	- 3.11.0 - [#7375] - This type is part of jOOQ's internal API. Do not reference this type directly from client code. Referencing this type before the SQLDataType class has been initialised may lead to deadlocks! See https://github.com/jOOQ/jOOQ/issues/3777 for details. Use the corresponding SQLDataType instead.
org.jooq.util.ase.ASEDSL	- 3.15.0 - [#10796] - This class will be removed, soon, no more vendor specific DSL API will be added.
org.jooq.util.auroramysql.AuroraMySQLDataType	- 3.11.0 - [#7375] - This type is part of jOOQ's internal API. Do not reference this type directly from client code. Referencing this type before the SQLDataType class has been initialised may lead to deadlocks! See https://github.com/jOOQ/jOOQ/issues/3777 for details. Use the corresponding SQLDataType instead.
org.jooq.util.aurorapostgres.AuroraPostgresDataType	- 3.11.0 - [#7375] - This type is part of jOOQ's internal API. Do not reference this type directly from client code. Referencing this type before the SQLDataType class has been initialised may lead to deadlocks! See https://github.com/jOOQ/jOOQ/issues/3777 for details. Use the corresponding SQLDataType instead.
org.jooq.util.bigquery.BigQueryDataType	- 3.11.0 - [#7375] - This type is part of jOOQ's internal API. Do not reference this type directly from client code. Referencing this type before the SQLDataType class has been initialised may lead to deadlocks! See https://github.com/jOOQ/jOOQ/issues/3777 for details. Use the corresponding SQLDataType instead.
org.jooq.util.cockroachdb.CockroachDBDataType	- 3.11.0 - [#7375] - This type is part of jOOQ's internal API. Do not reference this type directly from client code. Referencing this type before the SQLDataType class has been initialised may lead to deadlocks! See https://github.com/jOOQ/jOOQ/issues/3777 for details. Use the corresponding SQLDataType instead.
org.jooq.util.cubrid.CUBRIDDataType	- 3.11.0 - [#7375] - This type is part of jOOQ's internal API. Do not reference this type directly from client code. Referencing this type before the SQLDataType class has been initialised may lead to deadlocks! See https://github.com/jOOQ/jOOQ/issues/3777 for details. Use the corresponding SQLDataType instead.
org.jooq.util.cubrid.CUBRIDDSL	- 3.13.0 - [#9403] - This dialect is hardly used by anyone with jOOQ or without jOOQ and will be removed in the near future.
org.jooq.util.db2.DB2DataType	- 3.11.0 - [#7375] - This type is part of jOOQ's internal API. Do not reference this type directly from client code. Referencing this type before the SQLDataType class has been initialised may lead to deadlocks! See https://github.com/jOOQ/jOOQ/issues/3777 for details. Use the corresponding SQLDataType instead.
org.jooq.util.db2.DB2DSL	- 3.15.0 - [#10796] - This class will be removed, soon, no more vendor specific DSL API will be added.
org.jooq.util.derby.DerbyDataType	- 3.11.0 - [#7375] - This type is part of jOOQ's internal API. Do not reference this type directly from client code. Referencing this type before the SQLDataType class has been initialised may lead to deadlocks! See https://github.com/jOOQ/jOOQ/issues/3777 for details. Use the corresponding SQLDataType instead.
org.jooq.util.derby.DerbyDSL	- 3.15.0 - [#10796] - This class will be removed, soon, no more vendor specific DSL API will be added.
org.jooq.util.exasol.ExasolDataType	- 3.11.0 - [#7375] - This type is part of jOOQ's internal API. Do not reference this type directly from client code. Referencing this type before the SQLDataType class has been initialised may lead to deadlocks! See https://github.com/jOOQ/jOOQ/issues/3777 for details. Use the corresponding SQLDataType instead.
org.jooq.util.firebird.FirebirdDataType	- 3.11.0 - [#7375] - This type is part of jOOQ's internal API. Do not reference this type directly from client code. Referencing this type before the SQLDataType class has been initialised may lead to deadlocks! See https://github.com/jOOQ/jOOQ/issues/3777 for details. Use the corresponding SQLDataType instead.
org.jooq.util.firebird.FirebirdDSL	- 3.15.0 - [#10796] - This class will be removed, soon, no more vendor specific DSL API will be added.
org.jooq.util.h2.H2DataType	- 3.11.0 - [#7375] - This type is part of jOOQ's internal API. Do not reference this type directly from client code. Referencing this type before the SQLDataType class has been initialised may lead to deadlocks! See https://github.com/jOOQ/jOOQ/issues/3777 for details. Use the corresponding SQLDataType instead.
org.jooq.util.h2.H2DSL	- 3.15.0 - [#10796] - This class will be removed, soon, no more vendor specific DSL API will be added.
org.jooq.util.hana.HanaDataType	- 3.11.0 - [#7375] - This type is part of jOOQ's internal API. Do not reference this type directly from client code. Referencing this type before the SQLDataType class has been initialised may lead to deadlocks! See https://github.com/jOOQ/jOOQ/issues/3777 for details. Use the corresponding SQLDataType instead.
org.jooq.util.hana.HanaDSL	- 3.15.0 - [#10796] - This class will be removed, soon, no more vendor specific DSL API will be added.
org.jooq.util.hsqldb.HSQLDBDataType	- 3.11.0 - [#7375] - This type is part of jOOQ's internal API. Do not reference this type directly from client code. Referencing this type before the SQLDataType class has been initialised may lead to deadlocks! See https://github.com/jOOQ/jOOQ/issues/3777 for details. Use the corresponding SQLDataType instead.
org.jooq.util.hsqldb.HSQLDBDSL	- 3.15.0 - [#10796] - This class will be removed, soon, no more vendor specific DSL API will be added.
org.jooq.util.ignite.IgniteDataType	- 3.11.0 - [#7375] - This type is part of jOOQ's internal API. Do not reference this type directly from client code. Referencing this type before the SQLDataType class has been initialised may lead to deadlocks! See https://github.com/jOOQ/jOOQ/issues/3777 for details. Use the corresponding SQLDataType instead.
org.jooq.util.informix.InformixDataType	- 3.11.0 - [#7375] - This type is part of jOOQ's internal API. Do not reference this type directly from client code. Referencing this type before the SQLDataType class has been initialised may lead to deadlocks! See https://github.com/jOOQ/jOOQ/issues/3777 for details. Use the corresponding SQLDataType instead.
org.jooq.util.informix.InformixDSL	- 3.15.0 - [#10796] - This class will be removed, soon, no more vendor specific DSL API will be added.
org.jooq.util.ingres.IngresDataType	- 3.11.0 - [#7375] - This type is part of jOOQ's internal API. Do not reference this type directly from client code. Referencing this type before the SQLDataType class has been initialised may lead to deadlocks! See https://github.com/jOOQ/jOOQ/issues/3777 for details. Use the corresponding SQLDataType instead.
org.jooq.util.ingres.IngresDSL	- 3.15.0 - [#10796] - This class will be removed, soon, no more vendor specific DSL API will be added.
org.jooq.util.mariadb.MariaDBDataType	- 3.11.0 - [#7375] - This type is part of jOOQ's internal API. Do not reference this type directly from client code. Referencing this type before the SQLDataType class has been initialised may lead to deadlocks! See https://github.com/jOOQ/jOOQ/issues/3777 for details. Use the corresponding SQLDataType instead.
org.jooq.util.memsql.MemSQLDataType	- 3.11.0 - [#7375] - This type is part of jOOQ's internal API. Do not reference this type directly from client code. Referencing this type before the SQLDataType class has been initialised may lead to deadlocks! See https://github.com/jOOQ/jOOQ/issues/3777 for details. Use the corresponding SQLDataType instead.
org.jooq.util.mysql.MySQLDataType	- 3.11.0 - [#7375] - This type is part of jOOQ's internal API. Do not reference this type directly from client code. Referencing this type before the SQLDataType class has been initialised may lead to deadlocks! See https://github.com/jOOQ/jOOQ/issues/3777 for details. Use the corresponding SQLDataType instead.
org.jooq.util.mysql.MySQLDSL.decode(byte[], byte[])	- 3.15.0 - [#8611] - This function has been removed from MySQL 8
org.jooq.util.mysql.MySQLDSL.decode(String, String)	- 3.15.0 - [#8611] - This function has been removed from MySQL 8
org.jooq.util.mysql.MySQLDSL.decode(Field<T>, Field<T>)	- 3.15.0 - [#8611] - This function has been removed from MySQL 8
org.jooq.util.mysql.MySQLDSL.desDecrypt(byte[])	- 3.15.0 - [#8611] - This function has been removed from MySQL 8
org.jooq.util.mysql.MySQLDSL.desDecrypt(byte[], byte[])	- 3.15.0 - [#8611] - This function has been removed from MySQL 8
org.jooq.util.mysql.MySQLDSL.desDecrypt(String)	- 3.15.0 - [#8611] - This function has been removed from MySQL 8
org.jooq.util.mysql.MySQLDSL.desDecrypt(String, String)	- 3.15.0 - [#8611] - This function has been removed from MySQL 8
org.jooq.util.mysql.MySQLDSL.desDecrypt(Field<T>)	- 3.15.0 - [#8611] - This function has been removed from MySQL 8
org.jooq.util.mysql.MySQLDSL.desDecrypt(Field<T>, Field<T>)	- 3.15.0 - [#8611] - This function has been removed from MySQL 8
org.jooq.util.mysql.MySQLDSL.desEncrypt(byte[])	- 3.15.0 - [#8611] - This function has been removed from MySQL 8
org.jooq.util.mysql.MySQLDSL.desEncrypt(byte[], byte[])	- 3.15.0 - [#8611] - This function has been removed from MySQL 8
org.jooq.util.mysql.MySQLDSL.desEncrypt(String)	- 3.15.0 - [#8611] - This function has been removed from MySQL 8
org.jooq.util.mysql.MySQLDSL.desEncrypt(String, String)	- 3.15.0 - [#8611] - This function has been removed from MySQL 8
org.jooq.util.mysql.MySQLDSL.desEncrypt(Field<T>)	- 3.15.0 - [#8611] - This function has been removed from MySQL 8
org.jooq.util.mysql.MySQLDSL.desEncrypt(Field<T>, Field<T>)	- 3.15.0 - [#8611] - This function has been removed from MySQL 8
org.jooq.util.mysql.MySQLDSL.encode(byte[], byte[])	- 3.15.0 - [#8611] - This function has been removed from MySQL 8
org.jooq.util.mysql.MySQLDSL.encode(String, String)	- 3.15.0 - [#8611] - This function has been removed from MySQL 8
org.jooq.util.mysql.MySQLDSL.encode(Field<T>, Field<T>)	- 3.15.0 - [#8611] - This function has been removed from MySQL 8
org.jooq.util.mysql.MySQLDSL.password(byte[])	- 3.15.0 - [#8611] - This function has been removed from MySQL 8
org.jooq.util.mysql.MySQLDSL.password(String)	- 3.15.0 - [#8611] - This function has been removed from MySQL 8
org.jooq.util.mysql.MySQLDSL.password(Field<T>)	- 3.15.0 - [#8611] - This function has been removed from MySQL 8
org.jooq.util.mysql.MySQLDSL.values(Field<T>)	- 3.15.0 - [#12099] - MySQL 8.0.20 has deprecated this clause and replaced it by something new, which we'll support soon, see https://dev.mysql.com/doc/refman/8.0/en/insert-on-duplicate.html/ and https://github.com/jOOQ/jOOQ/issues/12099
org.jooq.util.oracle.OracleDataType	- 3.11.0 - [#7375] - This type is part of jOOQ's internal API. Do not reference this type directly from client code. Referencing this type before the SQLDataType class has been initialised may lead to deadlocks! See https://github.com/jOOQ/jOOQ/issues/3777 for details. Use the corresponding SQLDataType instead.
org.jooq.util.oracle.OracleDSL.toChar(Object)	- 3.14.0 - [#8381] [#10641] - Use DSL.toChar(Field, Field) instead.
org.jooq.util.oracle.OracleDSL.toChar(Object, String)	- 3.14.0 - [#8381] [#10641] - Use DSL.toChar(Field, Field) instead.
org.jooq.util.oracle.OracleDSL.toChar(Object, Field<String>)	- 3.14.0 - [#8381] [#10641] - Use DSL.toChar(Field, Field) instead.
org.jooq.util.oracle.OracleDSL.toChar(Field<?>)	- 3.14.0 - [#8381] [#10641] - Use DSL.toChar(Field, Field) instead.
org.jooq.util.oracle.OracleDSL.toChar(Field<?>, String)	- 3.14.0 - [#8381] [#10641] - Use DSL.toChar(Field, Field) instead.
org.jooq.util.oracle.OracleDSL.toChar(Field<?>, Field<String>)	- 3.14.0 - [#8381] [#10641] - Use DSL.toChar(Field, Field) instead.
org.jooq.util.postgres.PostgresDataType	- 3.11.0 - [#7375] - This type is part of jOOQ's internal API. Do not reference this type directly from client code. Referencing this type before the SQLDataType class has been initialised may lead to deadlocks! See https://github.com/jOOQ/jOOQ/issues/3777 for details. Use the corresponding SQLDataType instead.
org.jooq.util.postgres.PostgresDSL.oid(Table<?>)	- [#12420] - 3.16.0 - Use actual OID column references in jOOQ-meta, instead.
org.jooq.util.redshift.RedshiftDataType	- 3.11.0 - [#7375] - This type is part of jOOQ's internal API. Do not reference this type directly from client code. Referencing this type before the SQLDataType class has been initialised may lead to deadlocks! See https://github.com/jOOQ/jOOQ/issues/3777 for details. Use the corresponding SQLDataType instead.
org.jooq.util.redshift.RedshiftDSL	- 3.15.0 - [#10796] - This class will be removed, soon, no more vendor specific DSL API will be added.
org.jooq.util.snowflake.SnowflakeDataType	- 3.11.0 - [#7375] - This type is part of jOOQ's internal API. Do not reference this type directly from client code. Referencing this type before the SQLDataType class has been initialised may lead to deadlocks! See https://github.com/jOOQ/jOOQ/issues/3777 for details. Use the corresponding SQLDataType instead.
org.jooq.util.sqldatawarehouse.SQLDataWarehouseDataType	- 3.11.0 - [#7375] - This type is part of jOOQ's internal API. Do not reference this type directly from client code. Referencing this type before the SQLDataType class has been initialised may lead to deadlocks! See https://github.com/jOOQ/jOOQ/issues/3777 for details. Use the corresponding SQLDataType instead.
org.jooq.util.sqlite.SQLiteDataType	- 3.11.0 - [#7375] - This type is part of jOOQ's internal API. Do not reference this type directly from client code. Referencing this type before the SQLDataType class has been initialised may lead to deadlocks! See https://github.com/jOOQ/jOOQ/issues/3777 for details. Use the corresponding SQLDataType instead.
org.jooq.util.sqlite.SQLiteDSL	- 3.15.0 - [#10796] - This class will be removed, soon, no more vendor specific DSL API will be added.
org.jooq.util.sqlserver.SQLServerDataType	- 3.11.0 - [#7375] - This type is part of jOOQ's internal API. Do not reference this type directly from client code. Referencing this type before the SQLDataType class has been initialised may lead to deadlocks! See https://github.com/jOOQ/jOOQ/issues/3777 for details. Use the corresponding SQLDataType instead.
org.jooq.util.sybase.SybaseDataType	- 3.11.0 - [#7375] - This type is part of jOOQ's internal API. Do not reference this type directly from client code. Referencing this type before the SQLDataType class has been initialised may lead to deadlocks! See https://github.com/jOOQ/jOOQ/issues/3777 for details. Use the corresponding SQLDataType instead.
org.jooq.util.sybase.SybaseDSL	- 3.15.0 - [#10796] - This class will be removed, soon, no more vendor specific DSL API will be added.
org.jooq.util.teradata.TeradataDataType	- 3.11.0 - [#7375] - This type is part of jOOQ's internal API. Do not reference this type directly from client code. Referencing this type before the SQLDataType class has been initialised may lead to deadlocks! See https://github.com/jOOQ/jOOQ/issues/3777 for details. Use the corresponding SQLDataType instead.
org.jooq.util.vertica.VerticaDataType	- 3.11.0 - [#7375] - This type is part of jOOQ's internal API. Do not reference this type directly from client code. Referencing this type before the SQLDataType class has been initialised may lead to deadlocks! See https://github.com/jOOQ/jOOQ/issues/3777 for details. Use the corresponding SQLDataType instead.
org.jooq.util.vertica.VerticaDSL	- 3.15.0 - [#10796] - This class will be removed, soon, no more vendor specific DSL API will be added.
org.jooq.util.yugabytedb.YugabyteDBDataType	- 3.11.0 - [#7375] - This type is part of jOOQ's internal API. Do not reference this type directly from client code. Referencing this type before the SQLDataType class has been initialised may lead to deadlocks! See https://github.com/jOOQ/jOOQ/issues/3777 for details. Use the corresponding SQLDataType instead.
org.jooq.WindowFinalStep	- [#11329] - 3.15.0 - This type will be removed in the future. Do not reference it directly
org.jooq.WindowPartitionByStep.partitionByOne()	- 3.10 - [#6427] - This synthetic clause is no longer supported, use WindowPartitionByStep.partitionBy(Field...) instead, or omit the clause entirely.
org.jooq.WindowSpecificationFinalStep	- [#11329] - 3.15.0 - This type will be removed in the future. Do not reference it directly
org.jooq.WindowSpecificationPartitionByStep.partitionByOne()	- 3.10 - [#6427] - This synthetic clause is no longer supported, use WindowSpecificationPartitionByStep.partitionBy(Field...) instead, or omit the clause entirely.
org.jooq.WithStep.mergeInto(Table<R>, Field<T1>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via WithStep.mergeInto(Table)
org.jooq.WithStep.mergeInto(Table<R>, Field<T1>, Field<T2>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via WithStep.mergeInto(Table)
org.jooq.WithStep.mergeInto(Table<R>, Field<T1>, Field<T2>, Field<T3>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via WithStep.mergeInto(Table)
org.jooq.WithStep.mergeInto(Table<R>, Field<T1>, Field<T2>, Field<T3>, Field<T4>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via WithStep.mergeInto(Table)
org.jooq.WithStep.mergeInto(Table<R>, Field<T1>, Field<T2>, Field<T3>, Field<T4>, Field<T5>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via WithStep.mergeInto(Table)
org.jooq.WithStep.mergeInto(Table<R>, Field<T1>, Field<T2>, Field<T3>, Field<T4>, Field<T5>, Field<T6>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via WithStep.mergeInto(Table)
org.jooq.WithStep.mergeInto(Table<R>, Field<T1>, Field<T2>, Field<T3>, Field<T4>, Field<T5>, Field<T6>, Field<T7>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via WithStep.mergeInto(Table)
org.jooq.WithStep.mergeInto(Table<R>, Field<T1>, Field<T2>, Field<T3>, Field<T4>, Field<T5>, Field<T6>, Field<T7>, Field<T8>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via WithStep.mergeInto(Table)
org.jooq.WithStep.mergeInto(Table<R>, Field<T1>, Field<T2>, Field<T3>, Field<T4>, Field<T5>, Field<T6>, Field<T7>, Field<T8>, Field<T9>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via WithStep.mergeInto(Table)
org.jooq.WithStep.mergeInto(Table<R>, Field<T1>, Field<T2>, Field<T3>, Field<T4>, Field<T5>, Field<T6>, Field<T7>, Field<T8>, Field<T9>, Field<T10>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via WithStep.mergeInto(Table)
org.jooq.WithStep.mergeInto(Table<R>, Field<T1>, Field<T2>, Field<T3>, Field<T4>, Field<T5>, Field<T6>, Field<T7>, Field<T8>, Field<T9>, Field<T10>, Field<T11>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via WithStep.mergeInto(Table)
org.jooq.WithStep.mergeInto(Table<R>, Field<T1>, Field<T2>, Field<T3>, Field<T4>, Field<T5>, Field<T6>, Field<T7>, Field<T8>, Field<T9>, Field<T10>, Field<T11>, Field<T12>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via WithStep.mergeInto(Table)
org.jooq.WithStep.mergeInto(Table<R>, Field<T1>, Field<T2>, Field<T3>, Field<T4>, Field<T5>, Field<T6>, Field<T7>, Field<T8>, Field<T9>, Field<T10>, Field<T11>, Field<T12>, Field<T13>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via WithStep.mergeInto(Table)
org.jooq.WithStep.mergeInto(Table<R>, Field<T1>, Field<T2>, Field<T3>, Field<T4>, Field<T5>, Field<T6>, Field<T7>, Field<T8>, Field<T9>, Field<T10>, Field<T11>, Field<T12>, Field<T13>, Field<T14>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via WithStep.mergeInto(Table)
org.jooq.WithStep.mergeInto(Table<R>, Field<T1>, Field<T2>, Field<T3>, Field<T4>, Field<T5>, Field<T6>, Field<T7>, Field<T8>, Field<T9>, Field<T10>, Field<T11>, Field<T12>, Field<T13>, Field<T14>, Field<T15>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via WithStep.mergeInto(Table)
org.jooq.WithStep.mergeInto(Table<R>, Field<T1>, Field<T2>, Field<T3>, Field<T4>, Field<T5>, Field<T6>, Field<T7>, Field<T8>, Field<T9>, Field<T10>, Field<T11>, Field<T12>, Field<T13>, Field<T14>, Field<T15>, Field<T16>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via WithStep.mergeInto(Table)
org.jooq.WithStep.mergeInto(Table<R>, Field<T1>, Field<T2>, Field<T3>, Field<T4>, Field<T5>, Field<T6>, Field<T7>, Field<T8>, Field<T9>, Field<T10>, Field<T11>, Field<T12>, Field<T13>, Field<T14>, Field<T15>, Field<T16>, Field<T17>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via WithStep.mergeInto(Table)
org.jooq.WithStep.mergeInto(Table<R>, Field<T1>, Field<T2>, Field<T3>, Field<T4>, Field<T5>, Field<T6>, Field<T7>, Field<T8>, Field<T9>, Field<T10>, Field<T11>, Field<T12>, Field<T13>, Field<T14>, Field<T15>, Field<T16>, Field<T17>, Field<T18>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via WithStep.mergeInto(Table)
org.jooq.WithStep.mergeInto(Table<R>, Field<T1>, Field<T2>, Field<T3>, Field<T4>, Field<T5>, Field<T6>, Field<T7>, Field<T8>, Field<T9>, Field<T10>, Field<T11>, Field<T12>, Field<T13>, Field<T14>, Field<T15>, Field<T16>, Field<T17>, Field<T18>, Field<T19>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via WithStep.mergeInto(Table)
org.jooq.WithStep.mergeInto(Table<R>, Field<T1>, Field<T2>, Field<T3>, Field<T4>, Field<T5>, Field<T6>, Field<T7>, Field<T8>, Field<T9>, Field<T10>, Field<T11>, Field<T12>, Field<T13>, Field<T14>, Field<T15>, Field<T16>, Field<T17>, Field<T18>, Field<T19>, Field<T20>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via WithStep.mergeInto(Table)
org.jooq.WithStep.mergeInto(Table<R>, Field<T1>, Field<T2>, Field<T3>, Field<T4>, Field<T5>, Field<T6>, Field<T7>, Field<T8>, Field<T9>, Field<T10>, Field<T11>, Field<T12>, Field<T13>, Field<T14>, Field<T15>, Field<T16>, Field<T17>, Field<T18>, Field<T19>, Field<T20>, Field<T21>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via WithStep.mergeInto(Table)
org.jooq.WithStep.mergeInto(Table<R>, Field<T1>, Field<T2>, Field<T3>, Field<T4>, Field<T5>, Field<T6>, Field<T7>, Field<T8>, Field<T9>, Field<T10>, Field<T11>, Field<T12>, Field<T13>, Field<T14>, Field<T15>, Field<T16>, Field<T17>, Field<T18>, Field<T19>, Field<T20>, Field<T21>, Field<T22>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via WithStep.mergeInto(Table)
org.jooq.WithStep.with(String, BiFunction<? super Field<?>, ? super Integer, ? extends String>)	- 3.14.0 - [#10156] - These methods will be removed without replacement from a future jOOQ. They offer convenience that is unidiomatic for jOOQ's DSL, without offering functionality that would not be possible otherwise - yet they add complexity in jOOQ's internals.
org.jooq.WithStep.with(String, Function<? super Field<?>, ? extends String>)	- 3.14.0 - [#10156] - These methods will be removed without replacement from a future jOOQ. They offer convenience that is unidiomatic for jOOQ's DSL, without offering functionality that would not be possible otherwise - yet they add complexity in jOOQ's internals.

Deprecated Interfaces

Interface	Description
org.jooq.AlterDatabaseFinalStep	- [#11329] - 3.15.0 - This type will be removed in the future. Do not reference it directly Referencing XYZ*Step types directly from client code It is usually not recommended to reference any XYZ*Step types directly from client code, or assign them to local variables. When writing dynamic SQL, creating a statement's components dynamically, and passing them to the DSL API statically is usually a better choice. See the manual's section about dynamic SQL for details: https://www.jooq.org/doc/latest/manual/sql-building/dynamic-sql. Drawbacks of referencing the XYZ*Step types directly: They're operating on mutable implementations (as of jOOQ 3.x) They're less composable and not easy to get right when dynamic SQL gets complex They're less readable They might have binary incompatible changes between minor releases
org.jooq.AlterDomainFinalStep	- [#11329] - 3.15.0 - This type will be removed in the future. Do not reference it directly Referencing XYZ*Step types directly from client code It is usually not recommended to reference any XYZ*Step types directly from client code, or assign them to local variables. When writing dynamic SQL, creating a statement's components dynamically, and passing them to the DSL API statically is usually a better choice. See the manual's section about dynamic SQL for details: https://www.jooq.org/doc/latest/manual/sql-building/dynamic-sql. Drawbacks of referencing the XYZ*Step types directly: They're operating on mutable implementations (as of jOOQ 3.x) They're less composable and not easy to get right when dynamic SQL gets complex They're less readable They might have binary incompatible changes between minor releases
org.jooq.AlterIndexFinalStep	- [#11329] - 3.15.0 - This type will be removed in the future. Do not reference it directly Referencing XYZ*Step types directly from client code It is usually not recommended to reference any XYZ*Step types directly from client code, or assign them to local variables. When writing dynamic SQL, creating a statement's components dynamically, and passing them to the DSL API statically is usually a better choice. See the manual's section about dynamic SQL for details: https://www.jooq.org/doc/latest/manual/sql-building/dynamic-sql. Drawbacks of referencing the XYZ*Step types directly: They're operating on mutable implementations (as of jOOQ 3.x) They're less composable and not easy to get right when dynamic SQL gets complex They're less readable They might have binary incompatible changes between minor releases
org.jooq.AlterSchemaFinalStep	- [#11329] - 3.15.0 - This type will be removed in the future. Do not reference it directly Referencing XYZ*Step types directly from client code It is usually not recommended to reference any XYZ*Step types directly from client code, or assign them to local variables. When writing dynamic SQL, creating a statement's components dynamically, and passing them to the DSL API statically is usually a better choice. See the manual's section about dynamic SQL for details: https://www.jooq.org/doc/latest/manual/sql-building/dynamic-sql. Drawbacks of referencing the XYZ*Step types directly: They're operating on mutable implementations (as of jOOQ 3.x) They're less composable and not easy to get right when dynamic SQL gets complex They're less readable They might have binary incompatible changes between minor releases
org.jooq.AlterSequenceFinalStep	- [#11329] - 3.15.0 - This type will be removed in the future. Do not reference it directly Referencing XYZ*Step types directly from client code It is usually not recommended to reference any XYZ*Step types directly from client code, or assign them to local variables. When writing dynamic SQL, creating a statement's components dynamically, and passing them to the DSL API statically is usually a better choice. See the manual's section about dynamic SQL for details: https://www.jooq.org/doc/latest/manual/sql-building/dynamic-sql. Drawbacks of referencing the XYZ*Step types directly: They're operating on mutable implementations (as of jOOQ 3.x) They're less composable and not easy to get right when dynamic SQL gets complex They're less readable They might have binary incompatible changes between minor releases
org.jooq.AlterTableFinalStep	- [#11329] - 3.15.0 - This type will be removed in the future. Do not reference it directly
org.jooq.AlterTypeFinalStep	- [#11329] - 3.15.0 - This type will be removed in the future. Do not reference it directly Referencing XYZ*Step types directly from client code It is usually not recommended to reference any XYZ*Step types directly from client code, or assign them to local variables. When writing dynamic SQL, creating a statement's components dynamically, and passing them to the DSL API statically is usually a better choice. See the manual's section about dynamic SQL for details: https://www.jooq.org/doc/latest/manual/sql-building/dynamic-sql. Drawbacks of referencing the XYZ*Step types directly: They're operating on mutable implementations (as of jOOQ 3.x) They're less composable and not easy to get right when dynamic SQL gets complex They're less readable They might have binary incompatible changes between minor releases
org.jooq.AlterViewFinalStep	- [#11329] - 3.15.0 - This type will be removed in the future. Do not reference it directly Referencing XYZ*Step types directly from client code It is usually not recommended to reference any XYZ*Step types directly from client code, or assign them to local variables. When writing dynamic SQL, creating a statement's components dynamically, and passing them to the DSL API statically is usually a better choice. See the manual's section about dynamic SQL for details: https://www.jooq.org/doc/latest/manual/sql-building/dynamic-sql. Drawbacks of referencing the XYZ*Step types directly: They're operating on mutable implementations (as of jOOQ 3.x) They're less composable and not easy to get right when dynamic SQL gets complex They're less readable They might have binary incompatible changes between minor releases
org.jooq.CommentOnFinalStep	- [#11329] - 3.15.0 - This type will be removed in the future. Do not reference it directly Referencing XYZ*Step types directly from client code It is usually not recommended to reference any XYZ*Step types directly from client code, or assign them to local variables. When writing dynamic SQL, creating a statement's components dynamically, and passing them to the DSL API statically is usually a better choice. See the manual's section about dynamic SQL for details: https://www.jooq.org/doc/latest/manual/sql-building/dynamic-sql. Drawbacks of referencing the XYZ*Step types directly: They're operating on mutable implementations (as of jOOQ 3.x) They're less composable and not easy to get right when dynamic SQL gets complex They're less readable They might have binary incompatible changes between minor releases
org.jooq.ConditionProvider	- 2.6.0 [#1881] - This type will be removed from the public API, soon. Its methods will be pushed down into extending interfaces. Do not reference this type directly.
org.jooq.ConstraintFinalStep	- [#11329] - 3.15.0 - This type will be removed in the future. Do not reference it directly
org.jooq.CreateDatabaseFinalStep	- [#11329] - 3.15.0 - This type will be removed in the future. Do not reference it directly Referencing XYZ*Step types directly from client code It is usually not recommended to reference any XYZ*Step types directly from client code, or assign them to local variables. When writing dynamic SQL, creating a statement's components dynamically, and passing them to the DSL API statically is usually a better choice. See the manual's section about dynamic SQL for details: https://www.jooq.org/doc/latest/manual/sql-building/dynamic-sql. Drawbacks of referencing the XYZ*Step types directly: They're operating on mutable implementations (as of jOOQ 3.x) They're less composable and not easy to get right when dynamic SQL gets complex They're less readable They might have binary incompatible changes between minor releases
org.jooq.CreateDomainFinalStep	- [#11329] - 3.15.0 - This type will be removed in the future. Do not reference it directly Referencing XYZ*Step types directly from client code It is usually not recommended to reference any XYZ*Step types directly from client code, or assign them to local variables. When writing dynamic SQL, creating a statement's components dynamically, and passing them to the DSL API statically is usually a better choice. See the manual's section about dynamic SQL for details: https://www.jooq.org/doc/latest/manual/sql-building/dynamic-sql. Drawbacks of referencing the XYZ*Step types directly: They're operating on mutable implementations (as of jOOQ 3.x) They're less composable and not easy to get right when dynamic SQL gets complex They're less readable They might have binary incompatible changes between minor releases
org.jooq.CreateIndexFinalStep	- [#11329] - 3.15.0 - This type will be removed in the future. Do not reference it directly Referencing XYZ*Step types directly from client code It is usually not recommended to reference any XYZ*Step types directly from client code, or assign them to local variables. When writing dynamic SQL, creating a statement's components dynamically, and passing them to the DSL API statically is usually a better choice. See the manual's section about dynamic SQL for details: https://www.jooq.org/doc/latest/manual/sql-building/dynamic-sql. Drawbacks of referencing the XYZ*Step types directly: They're operating on mutable implementations (as of jOOQ 3.x) They're less composable and not easy to get right when dynamic SQL gets complex They're less readable They might have binary incompatible changes between minor releases
org.jooq.CreateSchemaFinalStep	- [#11329] - 3.15.0 - This type will be removed in the future. Do not reference it directly Referencing XYZ*Step types directly from client code It is usually not recommended to reference any XYZ*Step types directly from client code, or assign them to local variables. When writing dynamic SQL, creating a statement's components dynamically, and passing them to the DSL API statically is usually a better choice. See the manual's section about dynamic SQL for details: https://www.jooq.org/doc/latest/manual/sql-building/dynamic-sql. Drawbacks of referencing the XYZ*Step types directly: They're operating on mutable implementations (as of jOOQ 3.x) They're less composable and not easy to get right when dynamic SQL gets complex They're less readable They might have binary incompatible changes between minor releases
org.jooq.CreateSequenceFinalStep	- [#11329] - 3.15.0 - This type will be removed in the future. Do not reference it directly Referencing XYZ*Step types directly from client code It is usually not recommended to reference any XYZ*Step types directly from client code, or assign them to local variables. When writing dynamic SQL, creating a statement's components dynamically, and passing them to the DSL API statically is usually a better choice. See the manual's section about dynamic SQL for details: https://www.jooq.org/doc/latest/manual/sql-building/dynamic-sql. Drawbacks of referencing the XYZ*Step types directly: They're operating on mutable implementations (as of jOOQ 3.x) They're less composable and not easy to get right when dynamic SQL gets complex They're less readable They might have binary incompatible changes between minor releases
org.jooq.CreateTableFinalStep	- [#11329] - 3.15.0 - This type will be removed in the future. Do not reference it directly Referencing XYZ*Step types directly from client code It is usually not recommended to reference any XYZ*Step types directly from client code, or assign them to local variables. When writing dynamic SQL, creating a statement's components dynamically, and passing them to the DSL API statically is usually a better choice. See the manual's section about dynamic SQL for details: https://www.jooq.org/doc/latest/manual/sql-building/dynamic-sql. Drawbacks of referencing the XYZ*Step types directly: They're operating on mutable implementations (as of jOOQ 3.x) They're less composable and not easy to get right when dynamic SQL gets complex They're less readable They might have binary incompatible changes between minor releases
org.jooq.CreateTypeFinalStep	- [#11329] - 3.15.0 - This type will be removed in the future. Do not reference it directly
org.jooq.CreateViewFinalStep	- [#11329] - 3.15.0 - This type will be removed in the future. Do not reference it directly
org.jooq.DeleteFinalStep	- [#11329] - 3.15.0 - This type will be removed in the future. Do not reference it directly
org.jooq.DropDatabaseFinalStep	- [#11329] - 3.15.0 - This type will be removed in the future. Do not reference it directly Referencing XYZ*Step types directly from client code It is usually not recommended to reference any XYZ*Step types directly from client code, or assign them to local variables. When writing dynamic SQL, creating a statement's components dynamically, and passing them to the DSL API statically is usually a better choice. See the manual's section about dynamic SQL for details: https://www.jooq.org/doc/latest/manual/sql-building/dynamic-sql. Drawbacks of referencing the XYZ*Step types directly: They're operating on mutable implementations (as of jOOQ 3.x) They're less composable and not easy to get right when dynamic SQL gets complex They're less readable They might have binary incompatible changes between minor releases
org.jooq.DropDomainFinalStep	- [#11329] - 3.15.0 - This type will be removed in the future. Do not reference it directly Referencing XYZ*Step types directly from client code It is usually not recommended to reference any XYZ*Step types directly from client code, or assign them to local variables. When writing dynamic SQL, creating a statement's components dynamically, and passing them to the DSL API statically is usually a better choice. See the manual's section about dynamic SQL for details: https://www.jooq.org/doc/latest/manual/sql-building/dynamic-sql. Drawbacks of referencing the XYZ*Step types directly: They're operating on mutable implementations (as of jOOQ 3.x) They're less composable and not easy to get right when dynamic SQL gets complex They're less readable They might have binary incompatible changes between minor releases
org.jooq.DropIndexFinalStep	- [#11329] - 3.15.0 - This type will be removed in the future. Do not reference it directly Referencing XYZ*Step types directly from client code It is usually not recommended to reference any XYZ*Step types directly from client code, or assign them to local variables. When writing dynamic SQL, creating a statement's components dynamically, and passing them to the DSL API statically is usually a better choice. See the manual's section about dynamic SQL for details: https://www.jooq.org/doc/latest/manual/sql-building/dynamic-sql. Drawbacks of referencing the XYZ*Step types directly: They're operating on mutable implementations (as of jOOQ 3.x) They're less composable and not easy to get right when dynamic SQL gets complex They're less readable They might have binary incompatible changes between minor releases
org.jooq.DropSchemaFinalStep	- [#11329] - 3.15.0 - This type will be removed in the future. Do not reference it directly Referencing XYZ*Step types directly from client code It is usually not recommended to reference any XYZ*Step types directly from client code, or assign them to local variables. When writing dynamic SQL, creating a statement's components dynamically, and passing them to the DSL API statically is usually a better choice. See the manual's section about dynamic SQL for details: https://www.jooq.org/doc/latest/manual/sql-building/dynamic-sql. Drawbacks of referencing the XYZ*Step types directly: They're operating on mutable implementations (as of jOOQ 3.x) They're less composable and not easy to get right when dynamic SQL gets complex They're less readable They might have binary incompatible changes between minor releases
org.jooq.DropSequenceFinalStep	- [#11329] - 3.15.0 - This type will be removed in the future. Do not reference it directly Referencing XYZ*Step types directly from client code It is usually not recommended to reference any XYZ*Step types directly from client code, or assign them to local variables. When writing dynamic SQL, creating a statement's components dynamically, and passing them to the DSL API statically is usually a better choice. See the manual's section about dynamic SQL for details: https://www.jooq.org/doc/latest/manual/sql-building/dynamic-sql. Drawbacks of referencing the XYZ*Step types directly: They're operating on mutable implementations (as of jOOQ 3.x) They're less composable and not easy to get right when dynamic SQL gets complex They're less readable They might have binary incompatible changes between minor releases
org.jooq.DropTableFinalStep	- [#11329] - 3.15.0 - This type will be removed in the future. Do not reference it directly Referencing XYZ*Step types directly from client code It is usually not recommended to reference any XYZ*Step types directly from client code, or assign them to local variables. When writing dynamic SQL, creating a statement's components dynamically, and passing them to the DSL API statically is usually a better choice. See the manual's section about dynamic SQL for details: https://www.jooq.org/doc/latest/manual/sql-building/dynamic-sql. Drawbacks of referencing the XYZ*Step types directly: They're operating on mutable implementations (as of jOOQ 3.x) They're less composable and not easy to get right when dynamic SQL gets complex They're less readable They might have binary incompatible changes between minor releases
org.jooq.DropTypeFinalStep	- [#11329] - 3.15.0 - This type will be removed in the future. Do not reference it directly
org.jooq.DropViewFinalStep	- [#11329] - 3.15.0 - This type will be removed in the future. Do not reference it directly Referencing XYZ*Step types directly from client code It is usually not recommended to reference any XYZ*Step types directly from client code, or assign them to local variables. When writing dynamic SQL, creating a statement's components dynamically, and passing them to the DSL API statically is usually a better choice. See the manual's section about dynamic SQL for details: https://www.jooq.org/doc/latest/manual/sql-building/dynamic-sql. Drawbacks of referencing the XYZ*Step types directly: They're operating on mutable implementations (as of jOOQ 3.x) They're less composable and not easy to get right when dynamic SQL gets complex They're less readable They might have binary incompatible changes between minor releases
org.jooq.FieldOrConstraint	- 3.17.0 - [#13005] - Use TableElement instead.
org.jooq.GrantFinalStep	- [#11329] - 3.15.0 - This type will be removed in the future. Do not reference it directly Referencing XYZ*Step types directly from client code It is usually not recommended to reference any XYZ*Step types directly from client code, or assign them to local variables. When writing dynamic SQL, creating a statement's components dynamically, and passing them to the DSL API statically is usually a better choice. See the manual's section about dynamic SQL for details: https://www.jooq.org/doc/latest/manual/sql-building/dynamic-sql. Drawbacks of referencing the XYZ*Step types directly: They're operating on mutable implementations (as of jOOQ 3.x) They're less composable and not easy to get right when dynamic SQL gets complex They're less readable They might have binary incompatible changes between minor releases
org.jooq.InsertFinalStep	- [#11329] - 3.15.0 - This type will be removed in the future. Do not reference it directly
org.jooq.MergeFinalStep	- [#11329] - 3.15.0 - This type will be removed in the future. Do not reference it directly
org.jooq.MergeKeyStep1	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeKeyStep10	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeKeyStep11	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeKeyStep12	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeKeyStep13	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeKeyStep14	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeKeyStep15	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeKeyStep16	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeKeyStep17	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeKeyStep18	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeKeyStep19	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeKeyStep2	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeKeyStep20	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeKeyStep21	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeKeyStep22	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeKeyStep3	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeKeyStep4	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeKeyStep5	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeKeyStep6	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeKeyStep7	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeKeyStep8	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeKeyStep9	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeValuesStep1	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeValuesStep10	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeValuesStep11	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeValuesStep12	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeValuesStep13	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeValuesStep14	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeValuesStep15	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeValuesStep16	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeValuesStep17	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeValuesStep18	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeValuesStep19	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeValuesStep2	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeValuesStep20	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeValuesStep21	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeValuesStep22	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeValuesStep3	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeValuesStep4	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeValuesStep5	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeValuesStep6	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeValuesStep7	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeValuesStep8	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeValuesStep9	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.RecordHandler	- 3.15.0 - [#11902] - Use Iterable.forEach(Consumer) based methods, instead.
org.jooq.RevokeFinalStep	- [#11329] - 3.15.0 - This type will be removed in the future. Do not reference it directly Referencing XYZ*Step types directly from client code It is usually not recommended to reference any XYZ*Step types directly from client code, or assign them to local variables. When writing dynamic SQL, creating a statement's components dynamically, and passing them to the DSL API statically is usually a better choice. See the manual's section about dynamic SQL for details: https://www.jooq.org/doc/latest/manual/sql-building/dynamic-sql. Drawbacks of referencing the XYZ*Step types directly: They're operating on mutable implementations (as of jOOQ 3.x) They're less composable and not easy to get right when dynamic SQL gets complex They're less readable They might have binary incompatible changes between minor releases
org.jooq.TruncateFinalStep	- [#11329] - 3.15.0 - This type will be removed in the future. Do not reference it directly Referencing XYZ*Step types directly from client code It is usually not recommended to reference any XYZ*Step types directly from client code, or assign them to local variables. When writing dynamic SQL, creating a statement's components dynamically, and passing them to the DSL API statically is usually a better choice. See the manual's section about dynamic SQL for details: https://www.jooq.org/doc/latest/manual/sql-building/dynamic-sql. Drawbacks of referencing the XYZ*Step types directly: They're operating on mutable implementations (as of jOOQ 3.x) They're less composable and not easy to get right when dynamic SQL gets complex They're less readable They might have binary incompatible changes between minor releases
org.jooq.UpdateFinalStep	- [#11329] - 3.15.0 - This type will be removed in the future. Do not reference it directly
org.jooq.WindowFinalStep	- [#11329] - 3.15.0 - This type will be removed in the future. Do not reference it directly
org.jooq.WindowSpecificationFinalStep	- [#11329] - 3.15.0 - This type will be removed in the future. Do not reference it directly

Deprecated Classes

Class	Description
org.jooq.impl.AbstractKeys	- [#6875] [#7158] - 3.11.0 - Please re-generate your code
org.jooq.impl.DateToLocalDateConverter	- 3.15.0 - [#11505] - Use Converter.ofNullable(Class, Class, Function, Function) instead, e.g. Converter.ofNullable(Date.class, LocalDate.class, Date::toLocalDate, Date::valueOf).
org.jooq.impl.DefaultDiagnosticsListener	- 3.17.0 - [#13542] - This class is no longer needed. Implement the DiagnosticsListener SPI directly, instead.
org.jooq.impl.DefaultExecuteListener	- 3.17.0 - [#13542] - This class is no longer needed. Implement the ExecuteListener SPI directly, instead.
org.jooq.impl.DefaultMigrationListener	- 3.17.0 - [#13542] - This class is no longer needed. Implement the MigrationListener SPI directly, instead.
org.jooq.impl.DefaultParseListener	- 3.17.0 - [#13542] - This class is no longer needed. Implement the ParseListener SPI directly, instead.
org.jooq.impl.DefaultRecordListener	- 3.17.0 - [#13542] - This class is no longer needed. Implement the RecordListener SPI directly, instead.
org.jooq.impl.DefaultTransactionListener	- 3.17.0 - [#13542] - This class is no longer needed. Implement the TransactionListener SPI directly, instead.
org.jooq.impl.DefaultVisitListener	- 3.17.0 - [#13542] - This class is no longer needed. Implement the VisitListener SPI directly, instead.
org.jooq.impl.TimestampToLocalDateTimeConverter	- 3.15.0 - [#11505] - Use Converter.ofNullable(Class, Class, Function, Function) instead, e.g. Converter.ofNullable(Timestamp.class, LocalDateTime.class, Timestamp::toLocalDateTime, Timestamp::valueOf).
org.jooq.impl.TimeToLocalTimeConverter	- 3.15.0 - [#11505] - Use Converter.ofNullable(Class, Class, Function, Function) instead, e.g. Converter.ofNullable(Time.class, LocalTime.class, Time::toLocalTime, Time::valueOf).
org.jooq.SchemaMapping	- 2.0.5 - Use runtime configuration Settings instead
org.jooq.tools.Convert	- 3.15.0 - [#11898] This class will be removed in the future. Do not reuse. Data type conversion happens using internal Converter implementations, or ConverterProvider provided ones, or implementations attached to fields via generated code, or via Field.convert(Converter), or DataType.asConvertedDataType(Converter).
org.jooq.tools.jdbc.JDBC41Connection	- 3.15.0 - [#11618] - This type is no longer used by jOOQ and will be removed in the future.
org.jooq.tools.jdbc.JDBC41ResultSet	- 3.15.0 - [#11618] - This type is no longer used by jOOQ and will be removed in the future.
org.jooq.tools.jdbc.JDBC41Statement	- 3.15.0 - [#11618] - This type is no longer used by jOOQ and will be removed in the future.
org.jooq.util.access.AccessDataType	- 3.11.0 - [#7375] - This type is part of jOOQ's internal API. Do not reference this type directly from client code. Referencing this type before the SQLDataType class has been initialised may lead to deadlocks! See https://github.com/jOOQ/jOOQ/issues/3777 for details. Use the corresponding SQLDataType instead.
org.jooq.util.access.AccessDSL	- 3.15.0 - [#10796] - This class will be removed, soon, no more vendor specific DSL API will be added.
org.jooq.util.ase.ASEDataType	- 3.11.0 - [#7375] - This type is part of jOOQ's internal API. Do not reference this type directly from client code. Referencing this type before the SQLDataType class has been initialised may lead to deadlocks! See https://github.com/jOOQ/jOOQ/issues/3777 for details. Use the corresponding SQLDataType instead.
org.jooq.util.ase.ASEDSL	- 3.15.0 - [#10796] - This class will be removed, soon, no more vendor specific DSL API will be added.
org.jooq.util.auroramysql.AuroraMySQLDataType	- 3.11.0 - [#7375] - This type is part of jOOQ's internal API. Do not reference this type directly from client code. Referencing this type before the SQLDataType class has been initialised may lead to deadlocks! See https://github.com/jOOQ/jOOQ/issues/3777 for details. Use the corresponding SQLDataType instead.
org.jooq.util.aurorapostgres.AuroraPostgresDataType	- 3.11.0 - [#7375] - This type is part of jOOQ's internal API. Do not reference this type directly from client code. Referencing this type before the SQLDataType class has been initialised may lead to deadlocks! See https://github.com/jOOQ/jOOQ/issues/3777 for details. Use the corresponding SQLDataType instead.
org.jooq.util.bigquery.BigQueryDataType	- 3.11.0 - [#7375] - This type is part of jOOQ's internal API. Do not reference this type directly from client code. Referencing this type before the SQLDataType class has been initialised may lead to deadlocks! See https://github.com/jOOQ/jOOQ/issues/3777 for details. Use the corresponding SQLDataType instead.
org.jooq.util.cockroachdb.CockroachDBDataType	- 3.11.0 - [#7375] - This type is part of jOOQ's internal API. Do not reference this type directly from client code. Referencing this type before the SQLDataType class has been initialised may lead to deadlocks! See https://github.com/jOOQ/jOOQ/issues/3777 for details. Use the corresponding SQLDataType instead.
org.jooq.util.cubrid.CUBRIDDataType	- 3.11.0 - [#7375] - This type is part of jOOQ's internal API. Do not reference this type directly from client code. Referencing this type before the SQLDataType class has been initialised may lead to deadlocks! See https://github.com/jOOQ/jOOQ/issues/3777 for details. Use the corresponding SQLDataType instead.
org.jooq.util.cubrid.CUBRIDDSL	- 3.13.0 - [#9403] - This dialect is hardly used by anyone with jOOQ or without jOOQ and will be removed in the near future.
org.jooq.util.db2.DB2DataType	- 3.11.0 - [#7375] - This type is part of jOOQ's internal API. Do not reference this type directly from client code. Referencing this type before the SQLDataType class has been initialised may lead to deadlocks! See https://github.com/jOOQ/jOOQ/issues/3777 for details. Use the corresponding SQLDataType instead.
org.jooq.util.db2.DB2DSL	- 3.15.0 - [#10796] - This class will be removed, soon, no more vendor specific DSL API will be added.
org.jooq.util.derby.DerbyDataType	- 3.11.0 - [#7375] - This type is part of jOOQ's internal API. Do not reference this type directly from client code. Referencing this type before the SQLDataType class has been initialised may lead to deadlocks! See https://github.com/jOOQ/jOOQ/issues/3777 for details. Use the corresponding SQLDataType instead.
org.jooq.util.derby.DerbyDSL	- 3.15.0 - [#10796] - This class will be removed, soon, no more vendor specific DSL API will be added.
org.jooq.util.exasol.ExasolDataType	- 3.11.0 - [#7375] - This type is part of jOOQ's internal API. Do not reference this type directly from client code. Referencing this type before the SQLDataType class has been initialised may lead to deadlocks! See https://github.com/jOOQ/jOOQ/issues/3777 for details. Use the corresponding SQLDataType instead.
org.jooq.util.firebird.FirebirdDataType	- 3.11.0 - [#7375] - This type is part of jOOQ's internal API. Do not reference this type directly from client code. Referencing this type before the SQLDataType class has been initialised may lead to deadlocks! See https://github.com/jOOQ/jOOQ/issues/3777 for details. Use the corresponding SQLDataType instead.
org.jooq.util.firebird.FirebirdDSL	- 3.15.0 - [#10796] - This class will be removed, soon, no more vendor specific DSL API will be added.
org.jooq.util.h2.H2DataType	- 3.11.0 - [#7375] - This type is part of jOOQ's internal API. Do not reference this type directly from client code. Referencing this type before the SQLDataType class has been initialised may lead to deadlocks! See https://github.com/jOOQ/jOOQ/issues/3777 for details. Use the corresponding SQLDataType instead.
org.jooq.util.h2.H2DSL	- 3.15.0 - [#10796] - This class will be removed, soon, no more vendor specific DSL API will be added.
org.jooq.util.hana.HanaDataType	- 3.11.0 - [#7375] - This type is part of jOOQ's internal API. Do not reference this type directly from client code. Referencing this type before the SQLDataType class has been initialised may lead to deadlocks! See https://github.com/jOOQ/jOOQ/issues/3777 for details. Use the corresponding SQLDataType instead.
org.jooq.util.hana.HanaDSL	- 3.15.0 - [#10796] - This class will be removed, soon, no more vendor specific DSL API will be added.
org.jooq.util.hsqldb.HSQLDBDataType	- 3.11.0 - [#7375] - This type is part of jOOQ's internal API. Do not reference this type directly from client code. Referencing this type before the SQLDataType class has been initialised may lead to deadlocks! See https://github.com/jOOQ/jOOQ/issues/3777 for details. Use the corresponding SQLDataType instead.
org.jooq.util.hsqldb.HSQLDBDSL	- 3.15.0 - [#10796] - This class will be removed, soon, no more vendor specific DSL API will be added.
org.jooq.util.ignite.IgniteDataType	- 3.11.0 - [#7375] - This type is part of jOOQ's internal API. Do not reference this type directly from client code. Referencing this type before the SQLDataType class has been initialised may lead to deadlocks! See https://github.com/jOOQ/jOOQ/issues/3777 for details. Use the corresponding SQLDataType instead.
org.jooq.util.informix.InformixDataType	- 3.11.0 - [#7375] - This type is part of jOOQ's internal API. Do not reference this type directly from client code. Referencing this type before the SQLDataType class has been initialised may lead to deadlocks! See https://github.com/jOOQ/jOOQ/issues/3777 for details. Use the corresponding SQLDataType instead.
org.jooq.util.informix.InformixDSL	- 3.15.0 - [#10796] - This class will be removed, soon, no more vendor specific DSL API will be added.
org.jooq.util.ingres.IngresDataType	- 3.11.0 - [#7375] - This type is part of jOOQ's internal API. Do not reference this type directly from client code. Referencing this type before the SQLDataType class has been initialised may lead to deadlocks! See https://github.com/jOOQ/jOOQ/issues/3777 for details. Use the corresponding SQLDataType instead.
org.jooq.util.ingres.IngresDSL	- 3.15.0 - [#10796] - This class will be removed, soon, no more vendor specific DSL API will be added.
org.jooq.util.jaxb.tools.TrimAdapter	- 3.8.0 - [#4550] Do not reference this type directly.
org.jooq.util.mariadb.MariaDBDataType	- 3.11.0 - [#7375] - This type is part of jOOQ's internal API. Do not reference this type directly from client code. Referencing this type before the SQLDataType class has been initialised may lead to deadlocks! See https://github.com/jOOQ/jOOQ/issues/3777 for details. Use the corresponding SQLDataType instead.
org.jooq.util.memsql.MemSQLDataType	- 3.11.0 - [#7375] - This type is part of jOOQ's internal API. Do not reference this type directly from client code. Referencing this type before the SQLDataType class has been initialised may lead to deadlocks! See https://github.com/jOOQ/jOOQ/issues/3777 for details. Use the corresponding SQLDataType instead.
org.jooq.util.mysql.MySQLDataType	- 3.11.0 - [#7375] - This type is part of jOOQ's internal API. Do not reference this type directly from client code. Referencing this type before the SQLDataType class has been initialised may lead to deadlocks! See https://github.com/jOOQ/jOOQ/issues/3777 for details. Use the corresponding SQLDataType instead.
org.jooq.util.oracle.OracleDataType	- 3.11.0 - [#7375] - This type is part of jOOQ's internal API. Do not reference this type directly from client code. Referencing this type before the SQLDataType class has been initialised may lead to deadlocks! See https://github.com/jOOQ/jOOQ/issues/3777 for details. Use the corresponding SQLDataType instead.
org.jooq.util.postgres.PostgresDataType	- 3.11.0 - [#7375] - This type is part of jOOQ's internal API. Do not reference this type directly from client code. Referencing this type before the SQLDataType class has been initialised may lead to deadlocks! See https://github.com/jOOQ/jOOQ/issues/3777 for details. Use the corresponding SQLDataType instead.
org.jooq.util.redshift.RedshiftDataType	- 3.11.0 - [#7375] - This type is part of jOOQ's internal API. Do not reference this type directly from client code. Referencing this type before the SQLDataType class has been initialised may lead to deadlocks! See https://github.com/jOOQ/jOOQ/issues/3777 for details. Use the corresponding SQLDataType instead.
org.jooq.util.redshift.RedshiftDSL	- 3.15.0 - [#10796] - This class will be removed, soon, no more vendor specific DSL API will be added.
org.jooq.util.snowflake.SnowflakeDataType	- 3.11.0 - [#7375] - This type is part of jOOQ's internal API. Do not reference this type directly from client code. Referencing this type before the SQLDataType class has been initialised may lead to deadlocks! See https://github.com/jOOQ/jOOQ/issues/3777 for details. Use the corresponding SQLDataType instead.
org.jooq.util.sqldatawarehouse.SQLDataWarehouseDataType	- 3.11.0 - [#7375] - This type is part of jOOQ's internal API. Do not reference this type directly from client code. Referencing this type before the SQLDataType class has been initialised may lead to deadlocks! See https://github.com/jOOQ/jOOQ/issues/3777 for details. Use the corresponding SQLDataType instead.
org.jooq.util.sqlite.SQLiteDataType	- 3.11.0 - [#7375] - This type is part of jOOQ's internal API. Do not reference this type directly from client code. Referencing this type before the SQLDataType class has been initialised may lead to deadlocks! See https://github.com/jOOQ/jOOQ/issues/3777 for details. Use the corresponding SQLDataType instead.
org.jooq.util.sqlite.SQLiteDSL	- 3.15.0 - [#10796] - This class will be removed, soon, no more vendor specific DSL API will be added.
org.jooq.util.sqlserver.SQLServerDataType	- 3.11.0 - [#7375] - This type is part of jOOQ's internal API. Do not reference this type directly from client code. Referencing this type before the SQLDataType class has been initialised may lead to deadlocks! See https://github.com/jOOQ/jOOQ/issues/3777 for details. Use the corresponding SQLDataType instead.
org.jooq.util.sybase.SybaseDataType	- 3.11.0 - [#7375] - This type is part of jOOQ's internal API. Do not reference this type directly from client code. Referencing this type before the SQLDataType class has been initialised may lead to deadlocks! See https://github.com/jOOQ/jOOQ/issues/3777 for details. Use the corresponding SQLDataType instead.
org.jooq.util.sybase.SybaseDSL	- 3.15.0 - [#10796] - This class will be removed, soon, no more vendor specific DSL API will be added.
org.jooq.util.teradata.TeradataDataType	- 3.11.0 - [#7375] - This type is part of jOOQ's internal API. Do not reference this type directly from client code. Referencing this type before the SQLDataType class has been initialised may lead to deadlocks! See https://github.com/jOOQ/jOOQ/issues/3777 for details. Use the corresponding SQLDataType instead.
org.jooq.util.vertica.VerticaDataType	- 3.11.0 - [#7375] - This type is part of jOOQ's internal API. Do not reference this type directly from client code. Referencing this type before the SQLDataType class has been initialised may lead to deadlocks! See https://github.com/jOOQ/jOOQ/issues/3777 for details. Use the corresponding SQLDataType instead.
org.jooq.util.vertica.VerticaDSL	- 3.15.0 - [#10796] - This class will be removed, soon, no more vendor specific DSL API will be added.
org.jooq.util.yugabytedb.YugabyteDBDataType	- 3.11.0 - [#7375] - This type is part of jOOQ's internal API. Do not reference this type directly from client code. Referencing this type before the SQLDataType class has been initialised may lead to deadlocks! See https://github.com/jOOQ/jOOQ/issues/3777 for details. Use the corresponding SQLDataType instead.

Deprecated Enum Classes

Enum Class	Description
org.jooq.Clause	- 3.11.0 - [#7258] - This part of the VisitListener SPI is deprecated. There are currently no plans of replacing it. Please get in touch if you think this functionality needs to be kept in one way or another: https://github.com/jOOQ/jOOQ/issues/7258
org.jooq.conf.RenderKeywordStyle
org.jooq.conf.RenderNameStyle
org.jooq.tools.JooqLogger.Level	- Use Log.Level instead

Deprecated Exceptions

Exceptions	Description
org.jooq.impl.QOM.NotYetImplementedException	- [#12425] - 3.16.0 - Missing implementations should be added as soon as possible!

Deprecated Annotation Interfaces

Annotation Interface	Description
org.jooq.Internal	- 3.17.0 - [#13071] - Use ApiStatus.Internal instead.

Deprecated Fields

Field	Description
org.jooq.util.oracle.OracleDSL.DBMS_AQ.MESSAGE_PROPERTIES_T.expires	- use #expiration instead

Deprecated Methods

Method	Description
org.jooq.CloseableResultQuery.intern(int...)	- 3.10 - [#6254] - This functionality is no longer supported and will be removed in 4.0
org.jooq.CloseableResultQuery.intern(String...)	- 3.10 - [#6254] - This functionality is no longer supported and will be removed in 4.0
org.jooq.CloseableResultQuery.intern(Field<?>...)	- 3.10 - [#6254] - This functionality is no longer supported and will be removed in 4.0
org.jooq.CloseableResultQuery.intern(Name...)	- 3.10 - [#6254] - This functionality is no longer supported and will be removed in 4.0
org.jooq.Comparator.supportsNulls()	- 3.14.0 - [#9911] - This method is no longer supported.
org.jooq.Comparator.supportsQuantifier()	- 3.14.0 - [#9911] - This method is no longer supported.
org.jooq.Comparator.supportsSubselect()	- 3.14.0 - [#9911] - This method is no longer supported.
org.jooq.conf.Settings.getRenderKeywordStyle()	- 3.12.0 - [#5909] - Use RenderKeywordCase instead.
org.jooq.conf.Settings.getRenderNameStyle()	- 3.12.0 - [#5909] - Use RenderQuotedNames and RenderNameCase instead.
org.jooq.conf.Settings.setRenderKeywordStyle(RenderKeywordStyle)	- 3.12.0 - [#5909] - Use RenderKeywordCase instead.
org.jooq.conf.Settings.setRenderNameStyle(RenderNameStyle)	- 3.12.0 - [#5909] - Use RenderQuotedNames and RenderNameCase instead.
org.jooq.conf.Settings.withRenderKeywordStyle(RenderKeywordStyle)	- 3.12.0 - [#5909] - Use RenderKeywordCase instead.
org.jooq.conf.Settings.withRenderNameStyle(RenderNameStyle)	- 3.12.0 - [#5909] - Use RenderQuotedNames and RenderNameCase instead.
org.jooq.Configuration.schemaMapping()	- 2.0.5 - Use Configuration.settings() instead
org.jooq.Context.formatIndentLockEnd()	- [#10317] - 3.14.0 - Do not reuse this method. It will be removed without replacement.
org.jooq.Context.formatIndentLockStart()	- [#10317] - 3.14.0 - Do not reuse this method. It will be removed without replacement.
org.jooq.Context.keyword(String)	- 3.10.0 - [#4990] - Use DSL.keyword(String) instead.
org.jooq.Context.literal(String)	- 3.10.0 - [#4990] - Use any of DSL.name(String), DSL.quotedName(String) or DSL.unquotedName(String) instead.
org.jooq.Converters.of()	- [#10689] - 3.14.0 - This converter does not work. Do not use this method, use Converters.identity(Class) instead.
org.jooq.Converters.of(Converter<T, U>)	- [#10689] - 3.14.0 - This method does not provide any useful functionality and will be removed in the future.
org.jooq.Cursor.fetch(int)	- 3.10 - [#6363] - Use Cursor.fetchNext(int) instead.
org.jooq.Cursor.fetchInto(H)	- 3.15.0 - [#11902] - Use Iterable.forEach(Consumer) based methods, instead.
org.jooq.Cursor.fetchNextInto(H)	- 3.15.0 - [#11902] - Use Iterable.forEach(Consumer) based methods, instead.
org.jooq.Cursor.fetchOne()	- 3.10 - [#6363] - Use Cursor.fetchNext() instead.
org.jooq.Cursor.fetchOne(RecordMapper<? super R, E>)	- 3.10 - [#6363] - Use Cursor.fetchNext(RecordMapper) instead.
org.jooq.Cursor.fetchOneInto(H)	- 3.10 - [#6363] - Use Cursor.fetchNextInto(RecordHandler) instead.
org.jooq.Cursor.fetchOneInto(Class<? extends E>)	- 3.10 - [#6363] - Use Cursor.fetchNextInto(Class) instead.
org.jooq.Cursor.fetchOneInto(Table<Z>)	- 3.10 - [#6363] - Use Cursor.fetchNextInto(Table) instead.
org.jooq.Cursor.fetchOptional()	- 3.10 - [#6363] - Use Cursor.fetchNextOptional() instead.
org.jooq.Cursor.fetchOptional(RecordMapper<? super R, E>)	- 3.10 - [#6363] - Use Cursor.fetchNextOptional(RecordMapper) instead.
org.jooq.Cursor.fetchOptionalInto(Class<? extends E>)	- 3.10 - [#6363] - Use Cursor.fetchNextOptionalInto(Class) instead.
org.jooq.Cursor.fetchOptionalInto(Table<Z>)	- 3.10 - [#6363] - Use Cursor.fetchNextOptionalInto(Table) instead.
org.jooq.DataType.defaulted(boolean)	- [#3852] - 3.8.0 - Use DataType.defaultValue(Field) instead.
org.jooq.DSLContext.bindContext(PreparedStatement)	- [#6280] - 3.10 - Do not reuse this method. It will be completely internal with jOOQ 4.0
org.jooq.DSLContext.createOrReplaceView(String, BiFunction<? super Field<?>, ? super Integer, ? extends String>)	- 3.14.0 - [#10156] - These methods will be removed without replacement from a future jOOQ. They offer convenience that is unidiomatic for jOOQ's DSL, without offering functionality that would not be possible otherwise - yet they add complexity in jOOQ's internals.
org.jooq.DSLContext.createOrReplaceView(String, Function<? super Field<?>, ? extends String>)	- 3.14.0 - [#10156] - These methods will be removed without replacement from a future jOOQ. They offer convenience that is unidiomatic for jOOQ's DSL, without offering functionality that would not be possible otherwise - yet they add complexity in jOOQ's internals.
org.jooq.DSLContext.createOrReplaceView(Name, BiFunction<? super Field<?>, ? super Integer, ? extends Name>)	- 3.14.0 - [#10156] - These methods will be removed without replacement from a future jOOQ. They offer convenience that is unidiomatic for jOOQ's DSL, without offering functionality that would not be possible otherwise - yet they add complexity in jOOQ's internals.
org.jooq.DSLContext.createOrReplaceView(Name, Function<? super Field<?>, ? extends Name>)	- 3.14.0 - [#10156] - These methods will be removed without replacement from a future jOOQ. They offer convenience that is unidiomatic for jOOQ's DSL, without offering functionality that would not be possible otherwise - yet they add complexity in jOOQ's internals.
org.jooq.DSLContext.createOrReplaceView(Table<?>, BiFunction<? super Field<?>, ? super Integer, ? extends Field<?>>)	- 3.14.0 - [#10156] - These methods will be removed without replacement from a future jOOQ. They offer convenience that is unidiomatic for jOOQ's DSL, without offering functionality that would not be possible otherwise - yet they add complexity in jOOQ's internals.
org.jooq.DSLContext.createOrReplaceView(Table<?>, Function<? super Field<?>, ? extends Field<?>>)	- 3.14.0 - [#10156] - These methods will be removed without replacement from a future jOOQ. They offer convenience that is unidiomatic for jOOQ's DSL, without offering functionality that would not be possible otherwise - yet they add complexity in jOOQ's internals.
org.jooq.DSLContext.createView(String, BiFunction<? super Field<?>, ? super Integer, ? extends String>)	- 3.14.0 - [#10156] - These methods will be removed without replacement from a future jOOQ. They offer convenience that is unidiomatic for jOOQ's DSL, without offering functionality that would not be possible otherwise - yet they add complexity in jOOQ's internals.
org.jooq.DSLContext.createView(String, Function<? super Field<?>, ? extends String>)	- 3.14.0 - [#10156] - These methods will be removed without replacement from a future jOOQ. They offer convenience that is unidiomatic for jOOQ's DSL, without offering functionality that would not be possible otherwise - yet they add complexity in jOOQ's internals.
org.jooq.DSLContext.createView(Name, BiFunction<? super Field<?>, ? super Integer, ? extends Name>)	- 3.14.0 - [#10156] - These methods will be removed without replacement from a future jOOQ. They offer convenience that is unidiomatic for jOOQ's DSL, without offering functionality that would not be possible otherwise - yet they add complexity in jOOQ's internals.
org.jooq.DSLContext.createView(Name, Function<? super Field<?>, ? extends Name>)	- 3.14.0 - [#10156] - These methods will be removed without replacement from a future jOOQ. They offer convenience that is unidiomatic for jOOQ's DSL, without offering functionality that would not be possible otherwise - yet they add complexity in jOOQ's internals.
org.jooq.DSLContext.createView(Table<?>, BiFunction<? super Field<?>, ? super Integer, ? extends Field<?>>)	- 3.14.0 - [#10156] - These methods will be removed without replacement from a future jOOQ. They offer convenience that is unidiomatic for jOOQ's DSL, without offering functionality that would not be possible otherwise - yet they add complexity in jOOQ's internals.
org.jooq.DSLContext.createView(Table<?>, Function<? super Field<?>, ? extends Field<?>>)	- 3.14.0 - [#10156] - These methods will be removed without replacement from a future jOOQ. They offer convenience that is unidiomatic for jOOQ's DSL, without offering functionality that would not be possible otherwise - yet they add complexity in jOOQ's internals.
org.jooq.DSLContext.createViewIfNotExists(String, BiFunction<? super Field<?>, ? super Integer, ? extends String>)	- 3.14.0 - [#10156] - These methods will be removed without replacement from a future jOOQ. They offer convenience that is unidiomatic for jOOQ's DSL, without offering functionality that would not be possible otherwise - yet they add complexity in jOOQ's internals.
org.jooq.DSLContext.createViewIfNotExists(String, Function<? super Field<?>, ? extends String>)	- 3.14.0 - [#10156] - These methods will be removed without replacement from a future jOOQ. They offer convenience that is unidiomatic for jOOQ's DSL, without offering functionality that would not be possible otherwise - yet they add complexity in jOOQ's internals.
org.jooq.DSLContext.createViewIfNotExists(Name, BiFunction<? super Field<?>, ? super Integer, ? extends Name>)	- 3.14.0 - [#10156] - These methods will be removed without replacement from a future jOOQ. They offer convenience that is unidiomatic for jOOQ's DSL, without offering functionality that would not be possible otherwise - yet they add complexity in jOOQ's internals.
org.jooq.DSLContext.createViewIfNotExists(Name, Function<? super Field<?>, ? extends Name>)	- 3.14.0 - [#10156] - These methods will be removed without replacement from a future jOOQ. They offer convenience that is unidiomatic for jOOQ's DSL, without offering functionality that would not be possible otherwise - yet they add complexity in jOOQ's internals.
org.jooq.DSLContext.createViewIfNotExists(Table<?>, BiFunction<? super Field<?>, ? super Integer, ? extends Field<?>>)	- 3.14.0 - [#10156] - These methods will be removed without replacement from a future jOOQ. They offer convenience that is unidiomatic for jOOQ's DSL, without offering functionality that would not be possible otherwise - yet they add complexity in jOOQ's internals.
org.jooq.DSLContext.createViewIfNotExists(Table<?>, Function<? super Field<?>, ? extends Field<?>>)	- 3.14.0 - [#10156] - These methods will be removed without replacement from a future jOOQ. They offer convenience that is unidiomatic for jOOQ's DSL, without offering functionality that would not be possible otherwise - yet they add complexity in jOOQ's internals.
org.jooq.DSLContext.mergeInto(Table<R>, Collection<? extends Field<?>>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.DSLContext.mergeInto(Table<R>, Field<?>...)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.DSLContext.mergeInto(Table<R>, Field<T1>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.DSLContext.mergeInto(Table<R>, Field<T1>, Field<T2>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.DSLContext.mergeInto(Table<R>, Field<T1>, Field<T2>, Field<T3>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.DSLContext.mergeInto(Table<R>, Field<T1>, Field<T2>, Field<T3>, Field<T4>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.DSLContext.mergeInto(Table<R>, Field<T1>, Field<T2>, Field<T3>, Field<T4>, Field<T5>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.DSLContext.mergeInto(Table<R>, Field<T1>, Field<T2>, Field<T3>, Field<T4>, Field<T5>, Field<T6>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.DSLContext.mergeInto(Table<R>, Field<T1>, Field<T2>, Field<T3>, Field<T4>, Field<T5>, Field<T6>, Field<T7>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.DSLContext.mergeInto(Table<R>, Field<T1>, Field<T2>, Field<T3>, Field<T4>, Field<T5>, Field<T6>, Field<T7>, Field<T8>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.DSLContext.mergeInto(Table<R>, Field<T1>, Field<T2>, Field<T3>, Field<T4>, Field<T5>, Field<T6>, Field<T7>, Field<T8>, Field<T9>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.DSLContext.mergeInto(Table<R>, Field<T1>, Field<T2>, Field<T3>, Field<T4>, Field<T5>, Field<T6>, Field<T7>, Field<T8>, Field<T9>, Field<T10>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.DSLContext.mergeInto(Table<R>, Field<T1>, Field<T2>, Field<T3>, Field<T4>, Field<T5>, Field<T6>, Field<T7>, Field<T8>, Field<T9>, Field<T10>, Field<T11>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.DSLContext.mergeInto(Table<R>, Field<T1>, Field<T2>, Field<T3>, Field<T4>, Field<T5>, Field<T6>, Field<T7>, Field<T8>, Field<T9>, Field<T10>, Field<T11>, Field<T12>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.DSLContext.mergeInto(Table<R>, Field<T1>, Field<T2>, Field<T3>, Field<T4>, Field<T5>, Field<T6>, Field<T7>, Field<T8>, Field<T9>, Field<T10>, Field<T11>, Field<T12>, Field<T13>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.DSLContext.mergeInto(Table<R>, Field<T1>, Field<T2>, Field<T3>, Field<T4>, Field<T5>, Field<T6>, Field<T7>, Field<T8>, Field<T9>, Field<T10>, Field<T11>, Field<T12>, Field<T13>, Field<T14>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.DSLContext.mergeInto(Table<R>, Field<T1>, Field<T2>, Field<T3>, Field<T4>, Field<T5>, Field<T6>, Field<T7>, Field<T8>, Field<T9>, Field<T10>, Field<T11>, Field<T12>, Field<T13>, Field<T14>, Field<T15>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.DSLContext.mergeInto(Table<R>, Field<T1>, Field<T2>, Field<T3>, Field<T4>, Field<T5>, Field<T6>, Field<T7>, Field<T8>, Field<T9>, Field<T10>, Field<T11>, Field<T12>, Field<T13>, Field<T14>, Field<T15>, Field<T16>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.DSLContext.mergeInto(Table<R>, Field<T1>, Field<T2>, Field<T3>, Field<T4>, Field<T5>, Field<T6>, Field<T7>, Field<T8>, Field<T9>, Field<T10>, Field<T11>, Field<T12>, Field<T13>, Field<T14>, Field<T15>, Field<T16>, Field<T17>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.DSLContext.mergeInto(Table<R>, Field<T1>, Field<T2>, Field<T3>, Field<T4>, Field<T5>, Field<T6>, Field<T7>, Field<T8>, Field<T9>, Field<T10>, Field<T11>, Field<T12>, Field<T13>, Field<T14>, Field<T15>, Field<T16>, Field<T17>, Field<T18>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.DSLContext.mergeInto(Table<R>, Field<T1>, Field<T2>, Field<T3>, Field<T4>, Field<T5>, Field<T6>, Field<T7>, Field<T8>, Field<T9>, Field<T10>, Field<T11>, Field<T12>, Field<T13>, Field<T14>, Field<T15>, Field<T16>, Field<T17>, Field<T18>, Field<T19>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.DSLContext.mergeInto(Table<R>, Field<T1>, Field<T2>, Field<T3>, Field<T4>, Field<T5>, Field<T6>, Field<T7>, Field<T8>, Field<T9>, Field<T10>, Field<T11>, Field<T12>, Field<T13>, Field<T14>, Field<T15>, Field<T16>, Field<T17>, Field<T18>, Field<T19>, Field<T20>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.DSLContext.mergeInto(Table<R>, Field<T1>, Field<T2>, Field<T3>, Field<T4>, Field<T5>, Field<T6>, Field<T7>, Field<T8>, Field<T9>, Field<T10>, Field<T11>, Field<T12>, Field<T13>, Field<T14>, Field<T15>, Field<T16>, Field<T17>, Field<T18>, Field<T19>, Field<T20>, Field<T21>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.DSLContext.mergeInto(Table<R>, Field<T1>, Field<T2>, Field<T3>, Field<T4>, Field<T5>, Field<T6>, Field<T7>, Field<T8>, Field<T9>, Field<T10>, Field<T11>, Field<T12>, Field<T13>, Field<T14>, Field<T15>, Field<T16>, Field<T17>, Field<T18>, Field<T19>, Field<T20>, Field<T21>, Field<T22>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.DSLContext.renderContext()	- [#6280] - 3.10 - Do not reuse this method. It will be completely internal with jOOQ 4.0
org.jooq.DSLContext.with(String, BiFunction<? super Field<?>, ? super Integer, ? extends String>)	- 3.14.0 - [#10156] - These methods will be removed without replacement from a future jOOQ. They offer convenience that is unidiomatic for jOOQ's DSL, without offering functionality that would not be possible otherwise - yet they add complexity in jOOQ's internals.
org.jooq.DSLContext.with(String, Function<? super Field<?>, ? extends String>)	- 3.14.0 - [#10156] - These methods will be removed without replacement from a future jOOQ. They offer convenience that is unidiomatic for jOOQ's DSL, without offering functionality that would not be possible otherwise - yet they add complexity in jOOQ's internals.
org.jooq.DSLContext.withRecursive(String, BiFunction<? super Field<?>, ? super Integer, ? extends String>)	- 3.14.0 - [#10156] - These methods will be removed without replacement from a future jOOQ. They offer convenience that is unidiomatic for jOOQ's DSL, without offering functionality that would not be possible otherwise - yet they add complexity in jOOQ's internals.
org.jooq.DSLContext.withRecursive(String, Function<? super Field<?>, ? extends String>)	- 3.14.0 - [#10156] - These methods will be removed without replacement from a future jOOQ. They offer convenience that is unidiomatic for jOOQ's DSL, without offering functionality that would not be possible otherwise - yet they add complexity in jOOQ's internals.
org.jooq.Field.abs()	- 3.11 - [#7538] - Use DSL.abs(Field) instead.
org.jooq.Field.acos()	- 3.11 - [#7538] - Use DSL.acos(Field) instead.
org.jooq.Field.as(Function<? super Field<T>, ? extends String>)	- 3.14.0 - [#10156] - These methods will be removed without replacement from a future jOOQ. They offer convenience that is unidiomatic for jOOQ's DSL, without offering functionality that would not be possible otherwise - yet they add complexity in jOOQ's internals.
org.jooq.Field.ascii()	- 3.13 - [#9407] - Use DSL.ascii(Field) instead.
org.jooq.Field.asin()	- 3.11 - [#7538] - Use DSL.asin(Field) instead.
org.jooq.Field.atan()	- 3.11 - [#7538] - Use DSL.atan(Field) instead.
org.jooq.Field.atan2(Number)	- 3.11 - [#7538] - Use DSL.atan2(Field, Number) instead.
org.jooq.Field.atan2(Field<? extends Number>)	- 3.11 - [#7538] - Use DSL.atan2(Field, Field) instead.
org.jooq.Field.avg()	- 3.11 - [#7538] - Use DSL.avg(Field) instead.
org.jooq.Field.avgOver()	- 3.11 - [#7538] - Use DSL.avg(Field) instead.
org.jooq.Field.bitLength()	- 3.13 - [#9407] - Use DSL.bitLength(Field) instead.
org.jooq.Field.ceil()	- 3.11 - [#7538] - Use DSL.ceil(Field) instead.
org.jooq.Field.charLength()	- 3.13 - [#9407] - Use DSL.charLength(Field) instead.
org.jooq.Field.coalesce(Field<T>, Field<?>...)	- 3.13 - [#9407] - Use DSL.coalesce(Field, Field...) instead.
org.jooq.Field.coalesce(T, T...)	- 3.13 - [#9407] - Use DSL.coalesce(Object, Object...) instead.
org.jooq.Field.cos()	- 3.11 - [#7538] - Use DSL.cos(Field) instead.
org.jooq.Field.cosh()	- 3.11 - [#7538] - Use DSL.cosh(Field) instead.
org.jooq.Field.cot()	- 3.11 - [#7538] - Use DSL.cot(Field) instead.
org.jooq.Field.coth()	- 3.11 - [#7538] - Use DSL.coth(Field) instead.
org.jooq.Field.count()	- 3.11 - [#7538] - Use DSL.count(Field) instead.
org.jooq.Field.countDistinct()	- 3.11 - [#7538] - Use DSL.countDistinct(Field) instead.
org.jooq.Field.countOver()	- 3.11 - [#7538] - Use DSL.count(Field) instead.
org.jooq.Field.decode(Field<T>, Field<Z>)	- 3.13 - [#9407] - Use DSL.decode(Field, Field, Field) instead.
org.jooq.Field.decode(Field<T>, Field<Z>, Field<?>...)	- 3.13 - [#9407] - Use DSL.decode(Field, Field, Field, Field...) instead.
org.jooq.Field.decode(T, Z)	- 3.13 - [#9407] - Use DSL.decode(Object, Object, Object) instead.
org.jooq.Field.decode(T, Z, Object...)	- 3.13 - [#9407] - Use DSL.decode(Object, Object, Object, Object...) instead.
org.jooq.Field.deg()	- 3.11 - [#7538] - Use DSL.deg(Field) instead.
org.jooq.Field.exp()	- 3.11 - [#7538] - Use DSL.exp(Field) instead.
org.jooq.Field.extract(DatePart)	- 3.11 - [#7538] - Use DSL.extract(Field, DatePart) instead.
org.jooq.Field.firstValue()	- 3.11 - [#7538] - Use DSL.firstValue(Field) instead.
org.jooq.Field.floor()	- 3.11 - [#7538] - Use DSL.floor(Field) instead.
org.jooq.Field.greatest(Field<?>...)	- 3.11 - [#7538] - Use DSL.greatest(Field, Field...) instead.
org.jooq.Field.greatest(T...)	- 3.11 - [#7538] - Use DSL.greatest(Field, Field...) instead.
org.jooq.Field.lag()	- 3.11 - [#7538] - Use DSL.lag(Field) instead.
org.jooq.Field.lag(int)	- 3.11 - [#7538] - Use DSL.lag(Field, int) instead.
org.jooq.Field.lag(int, Field<T>)	- 3.11 - [#7538] - Use DSL.lag(Field, int, Field) instead.
org.jooq.Field.lag(int, T)	- 3.11 - [#7538] - Use DSL.lag(Field, int, Object) instead.
org.jooq.Field.lastValue()	- 3.11 - [#7538] - Use DSL.lastValue(Field) instead.
org.jooq.Field.lead()	- 3.11 - [#7538] - Use DSL.lead(Field) instead.
org.jooq.Field.lead(int)	- 3.11 - [#7538] - Use DSL.lead(Field, int) instead.
org.jooq.Field.lead(int, Field<T>)	- 3.11 - [#7538] - Use DSL.lead(Field, int, Field) instead.
org.jooq.Field.lead(int, T)	- 3.11 - [#7538] - Use DSL.lead(Field, int, Object) instead.
org.jooq.Field.least(Field<?>...)	- 3.11 - [#7538] - Use DSL.least(Field, Field...) instead.
org.jooq.Field.least(T...)	- 3.11 - [#7538] - Use DSL.least(Field, Field...) instead.
org.jooq.Field.length()	- 3.13 - [#9407] - Use DSL.length(Field) instead.
org.jooq.Field.ln()	- 3.11 - [#7538] - Use DSL.ln(Field) instead.
org.jooq.Field.log(int)	- 3.11 - [#7538] - Use DSL.log(Field, int) instead.
org.jooq.Field.lower()	- 3.13 - [#9407] - Use DSL.lower(Field) instead.
org.jooq.Field.lpad(int)	- 3.13 - [#9407] - Use DSL.lpad(Field, int) instead.
org.jooq.Field.lpad(int, char)	- 3.13 - [#9407] - Use DSL.lpad(Field, int, char) instead.
org.jooq.Field.lpad(Field<? extends Number>)	- 3.13 - [#9407] - Use DSL.lpad(Field, Field) instead.
org.jooq.Field.lpad(Field<? extends Number>, Field<String>)	- 3.13 - [#9407] - Use DSL.lpad(Field, Field, Field) instead.
org.jooq.Field.ltrim()	- 3.13 - [#9407] - Use DSL.ltrim(Field) instead.
org.jooq.Field.max()	- 3.11 - [#7538] - Use DSL.max(Field) instead.
org.jooq.Field.maxOver()	- 3.11 - [#7538] - Use DSL.max(Field) instead.
org.jooq.Field.median()	- 3.11 - [#7538] - Use DSL.median(Field) instead.
org.jooq.Field.min()	- 3.11 - [#7538] - Use DSL.min(Field) instead.
org.jooq.Field.minOver()	- 3.11 - [#7538] - Use DSL.min(Field) instead.
org.jooq.Field.nullif(Field<T>)	- 3.13 - [#9407] - Use DSL.nullif(Field, Field) instead.
org.jooq.Field.nullif(T)	- 3.13 - [#9407] - Use DSL.nullif(Field, Object) instead.
org.jooq.Field.nvl(Field<T>)	- 3.13 - [#9407] - Use DSL.nvl(Field, Field) instead.
org.jooq.Field.nvl(T)	- 3.13 - [#9407] - Use DSL.nvl(Field, Object) instead.
org.jooq.Field.nvl2(Field<Z>, Field<Z>)	- 3.13 - [#9407] - Use DSL.nvl2(Field, Field, Field) instead.
org.jooq.Field.nvl2(Z, Z)	- 3.13 - [#9407] - Use DSL.nvl2(Field, Object, Object) instead.
org.jooq.Field.octetLength()	- 3.13 - [#9407] - Use DSL.octetLength(Field) instead.
org.jooq.Field.position(String)	- 3.13 - [#9407] - Use DSL.position(Field, String) instead.
org.jooq.Field.position(Field<String>)	- 3.13 - [#9407] - Use DSL.position(Field, Field) instead.
org.jooq.Field.rad()	- 3.11 - [#7538] - Use DSL.rad(Field) instead.
org.jooq.Field.repeat(Number)	- 3.13 - [#9407] - Use DSL.repeat(Field, int) instead.
org.jooq.Field.repeat(Field<? extends Number>)	- 3.13 - [#9407] - Use DSL.repeat(Field, Field) instead.
org.jooq.Field.replace(String)	- 3.13 - [#9407] - Use DSL.replace(Field, String) instead.
org.jooq.Field.replace(String, String)	- 3.13 - [#9407] - Use DSL.replace(Field, String, String) instead.
org.jooq.Field.replace(Field<String>)	- 3.13 - [#9407] - Use DSL.replace(Field, Field) instead.
org.jooq.Field.replace(Field<String>, Field<String>)	- 3.13 - [#9407] - Use DSL.replace(Field, Field, Field) instead.
org.jooq.Field.round()	- 3.11 - [#7538] - Use DSL.round(Field) instead.
org.jooq.Field.round(int)	- 3.11 - [#7538] - Use DSL.round(Field, int) instead.
org.jooq.Field.rpad(int)	- 3.13 - [#9407] - Use DSL.rpad(Field, int) instead.
org.jooq.Field.rpad(int, char)	- 3.13 - [#9407] - Use DSL.rpad(Field, int, char) instead.
org.jooq.Field.rpad(Field<? extends Number>)	- 3.13 - [#9407] - Use DSL.rpad(Field, Field) instead.
org.jooq.Field.rpad(Field<? extends Number>, Field<String>)	- 3.13 - [#9407] - Use DSL.rpad(Field, Field, Field) instead.
org.jooq.Field.rtrim()	- 3.13 - [#9407] - Use DSL.rtrim(Field) instead.
org.jooq.Field.sign()	- 3.11 - [#7538] - Use DSL.sign(Field) instead.
org.jooq.Field.sin()	- 3.11 - [#7538] - Use DSL.sin(Field) instead.
org.jooq.Field.sinh()	- 3.11 - [#7538] - Use DSL.sinh(Field) instead.
org.jooq.Field.sqrt()	- 3.11 - [#7538] - Use DSL.sqrt(Field) instead.
org.jooq.Field.stddevPop()	- 3.11 - [#7538] - Use DSL.stddevPop(Field) instead.
org.jooq.Field.stddevPopOver()	- 3.11 - [#7538] - Use DSL.stddevPop(Field) instead.
org.jooq.Field.stddevSamp()	- 3.11 - [#7538] - Use DSL.stddevSamp(Field) instead.
org.jooq.Field.stddevSampOver()	- 3.11 - [#7538] - Use DSL.stddevSamp(Field) instead.
org.jooq.Field.substring(int)	- 3.13 - [#9407] - Use DSL.substring(Field, int) instead.
org.jooq.Field.substring(int, int)	- 3.13 - [#9407] - Use DSL.substring(Field, int, int) instead.
org.jooq.Field.substring(Field<? extends Number>)	- 3.13 - [#9407] - Use DSL.substring(Field, Field) instead.
org.jooq.Field.substring(Field<? extends Number>, Field<? extends Number>)	- 3.13 - [#9407] - Use DSL.substring(Field, Field, Field) instead.
org.jooq.Field.sum()	- 3.11 - [#7538] - Use DSL.sum(Field) instead.
org.jooq.Field.sumOver()	- 3.11 - [#7538] - Use DSL.sum(Field) instead.
org.jooq.Field.tan()	- 3.11 - [#7538] - Use DSL.tan(Field) instead.
org.jooq.Field.tanh()	- 3.11 - [#7538] - Use DSL.tanh(Field) instead.
org.jooq.Field.trim()	- 3.13 - [#9407] - Use DSL.trim(Field) instead.
org.jooq.Field.upper()	- 3.13 - [#9407] - Use DSL.upper(Field) instead.
org.jooq.Field.varPop()	- 3.11 - [#7538] - Use DSL.varPop(Field) instead.
org.jooq.Field.varPopOver()	- 3.11 - [#7538] - Use DSL.varPop(Field) instead.
org.jooq.Field.varSamp()	- 3.11 - [#7538] - Use DSL.varSamp(Field) instead.
org.jooq.Field.varSampOver()	- 3.11 - [#7538] - Use DSL.varSamp(Field) instead.
org.jooq.FieldLike.asField(Function<? super Field<T>, ? extends String>)	- 3.14.0 - [#10156] - These methods will be removed without replacement from a future jOOQ. They offer convenience that is unidiomatic for jOOQ's DSL, without offering functionality that would not be possible otherwise - yet they add complexity in jOOQ's internals.
org.jooq.impl.AbstractKeys.createForeignKey(UniqueKey<U>, Table<R>, String, TableField<R, ?>...)	- [#6875] [#7158] - 3.11.0 - Please re-generate your code
org.jooq.impl.AbstractKeys.createForeignKey(UniqueKey<U>, Table<R>, TableField<R, ?>...)	- [#6875] [#7158] - 3.11.0 - Please re-generate your code
org.jooq.impl.AbstractKeys.createIdentity(Table<R>, TableField<R, T>)	- [#6875] [#7158] - 3.11.0 - Please re-generate your code
org.jooq.impl.AbstractKeys.createIndex(String, Table<?>, OrderField<?>[], boolean)	- [#6875] [#7158] - 3.11.0 - Please re-generate your code
org.jooq.impl.AbstractKeys.createUniqueKey(Table<R>, String, TableField<R, ?>...)	- [#6875] [#7158] - 3.11.0 - Please re-generate your code
org.jooq.impl.AbstractKeys.createUniqueKey(Table<R>, TableField<R, ?>...)	- [#6875] [#7158] - 3.11.0 - Please re-generate your code
org.jooq.impl.AbstractRoutine.createParameter(String, DataType<T>)	- Please, re-generate your routine code.
org.jooq.impl.AbstractRoutine.createParameter(String, DataType<T>, boolean)	- Please, re-generate your routine code.
org.jooq.impl.AbstractRoutine.createParameter(String, DataType<T>, boolean, boolean)	- Please, re-generate your routine code.
org.jooq.impl.AbstractRoutine.createParameter(String, DataType<T>, boolean, boolean, Binding<T, U>)	- Please, re-generate your routine code.
org.jooq.impl.AbstractRoutine.createParameter(String, DataType<T>, boolean, boolean, Converter<T, U>)	- Please, re-generate your routine code.
org.jooq.impl.AbstractRoutine.createParameter(String, DataType<T>, boolean, boolean, Converter<X, U>, Binding<T, X>)	- Please, re-generate your routine code.
org.jooq.impl.AbstractRoutine.createParameter(String, DataType<T>, boolean, Binding<T, U>)	- Please, re-generate your routine code.
org.jooq.impl.AbstractRoutine.createParameter(String, DataType<T>, boolean, Converter<T, U>)	- Please, re-generate your routine code.
org.jooq.impl.AbstractRoutine.createParameter(String, DataType<T>, boolean, Converter<X, U>, Binding<T, X>)	- Please, re-generate your routine code.
org.jooq.impl.DefaultConfiguration.schemaMapping()
org.jooq.impl.DefaultDSLContext.mergeInto(Table<R>, Field<T1>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DefaultDSLContext.mergeInto(Table)
org.jooq.impl.DefaultDSLContext.mergeInto(Table<R>, Field<T1>, Field<T2>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DefaultDSLContext.mergeInto(Table)
org.jooq.impl.DefaultDSLContext.mergeInto(Table<R>, Field<T1>, Field<T2>, Field<T3>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DefaultDSLContext.mergeInto(Table)
org.jooq.impl.DefaultDSLContext.mergeInto(Table<R>, Field<T1>, Field<T2>, Field<T3>, Field<T4>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DefaultDSLContext.mergeInto(Table)
org.jooq.impl.DefaultDSLContext.mergeInto(Table<R>, Field<T1>, Field<T2>, Field<T3>, Field<T4>, Field<T5>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DefaultDSLContext.mergeInto(Table)
org.jooq.impl.DefaultDSLContext.mergeInto(Table<R>, Field<T1>, Field<T2>, Field<T3>, Field<T4>, Field<T5>, Field<T6>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DefaultDSLContext.mergeInto(Table)
org.jooq.impl.DefaultDSLContext.mergeInto(Table<R>, Field<T1>, Field<T2>, Field<T3>, Field<T4>, Field<T5>, Field<T6>, Field<T7>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DefaultDSLContext.mergeInto(Table)
org.jooq.impl.DefaultDSLContext.mergeInto(Table<R>, Field<T1>, Field<T2>, Field<T3>, Field<T4>, Field<T5>, Field<T6>, Field<T7>, Field<T8>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DefaultDSLContext.mergeInto(Table)
org.jooq.impl.DefaultDSLContext.mergeInto(Table<R>, Field<T1>, Field<T2>, Field<T3>, Field<T4>, Field<T5>, Field<T6>, Field<T7>, Field<T8>, Field<T9>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DefaultDSLContext.mergeInto(Table)
org.jooq.impl.DefaultDSLContext.mergeInto(Table<R>, Field<T1>, Field<T2>, Field<T3>, Field<T4>, Field<T5>, Field<T6>, Field<T7>, Field<T8>, Field<T9>, Field<T10>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DefaultDSLContext.mergeInto(Table)
org.jooq.impl.DefaultDSLContext.mergeInto(Table<R>, Field<T1>, Field<T2>, Field<T3>, Field<T4>, Field<T5>, Field<T6>, Field<T7>, Field<T8>, Field<T9>, Field<T10>, Field<T11>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DefaultDSLContext.mergeInto(Table)
org.jooq.impl.DefaultDSLContext.mergeInto(Table<R>, Field<T1>, Field<T2>, Field<T3>, Field<T4>, Field<T5>, Field<T6>, Field<T7>, Field<T8>, Field<T9>, Field<T10>, Field<T11>, Field<T12>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DefaultDSLContext.mergeInto(Table)
org.jooq.impl.DefaultDSLContext.mergeInto(Table<R>, Field<T1>, Field<T2>, Field<T3>, Field<T4>, Field<T5>, Field<T6>, Field<T7>, Field<T8>, Field<T9>, Field<T10>, Field<T11>, Field<T12>, Field<T13>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DefaultDSLContext.mergeInto(Table)
org.jooq.impl.DefaultDSLContext.mergeInto(Table<R>, Field<T1>, Field<T2>, Field<T3>, Field<T4>, Field<T5>, Field<T6>, Field<T7>, Field<T8>, Field<T9>, Field<T10>, Field<T11>, Field<T12>, Field<T13>, Field<T14>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DefaultDSLContext.mergeInto(Table)
org.jooq.impl.DefaultDSLContext.mergeInto(Table<R>, Field<T1>, Field<T2>, Field<T3>, Field<T4>, Field<T5>, Field<T6>, Field<T7>, Field<T8>, Field<T9>, Field<T10>, Field<T11>, Field<T12>, Field<T13>, Field<T14>, Field<T15>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DefaultDSLContext.mergeInto(Table)
org.jooq.impl.DefaultDSLContext.mergeInto(Table<R>, Field<T1>, Field<T2>, Field<T3>, Field<T4>, Field<T5>, Field<T6>, Field<T7>, Field<T8>, Field<T9>, Field<T10>, Field<T11>, Field<T12>, Field<T13>, Field<T14>, Field<T15>, Field<T16>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DefaultDSLContext.mergeInto(Table)
org.jooq.impl.DefaultDSLContext.mergeInto(Table<R>, Field<T1>, Field<T2>, Field<T3>, Field<T4>, Field<T5>, Field<T6>, Field<T7>, Field<T8>, Field<T9>, Field<T10>, Field<T11>, Field<T12>, Field<T13>, Field<T14>, Field<T15>, Field<T16>, Field<T17>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DefaultDSLContext.mergeInto(Table)
org.jooq.impl.DefaultDSLContext.mergeInto(Table<R>, Field<T1>, Field<T2>, Field<T3>, Field<T4>, Field<T5>, Field<T6>, Field<T7>, Field<T8>, Field<T9>, Field<T10>, Field<T11>, Field<T12>, Field<T13>, Field<T14>, Field<T15>, Field<T16>, Field<T17>, Field<T18>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DefaultDSLContext.mergeInto(Table)
org.jooq.impl.DefaultDSLContext.mergeInto(Table<R>, Field<T1>, Field<T2>, Field<T3>, Field<T4>, Field<T5>, Field<T6>, Field<T7>, Field<T8>, Field<T9>, Field<T10>, Field<T11>, Field<T12>, Field<T13>, Field<T14>, Field<T15>, Field<T16>, Field<T17>, Field<T18>, Field<T19>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DefaultDSLContext.mergeInto(Table)
org.jooq.impl.DefaultDSLContext.mergeInto(Table<R>, Field<T1>, Field<T2>, Field<T3>, Field<T4>, Field<T5>, Field<T6>, Field<T7>, Field<T8>, Field<T9>, Field<T10>, Field<T11>, Field<T12>, Field<T13>, Field<T14>, Field<T15>, Field<T16>, Field<T17>, Field<T18>, Field<T19>, Field<T20>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DefaultDSLContext.mergeInto(Table)
org.jooq.impl.DefaultDSLContext.mergeInto(Table<R>, Field<T1>, Field<T2>, Field<T3>, Field<T4>, Field<T5>, Field<T6>, Field<T7>, Field<T8>, Field<T9>, Field<T10>, Field<T11>, Field<T12>, Field<T13>, Field<T14>, Field<T15>, Field<T16>, Field<T17>, Field<T18>, Field<T19>, Field<T20>, Field<T21>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DefaultDSLContext.mergeInto(Table)
org.jooq.impl.DefaultDSLContext.mergeInto(Table<R>, Field<T1>, Field<T2>, Field<T3>, Field<T4>, Field<T5>, Field<T6>, Field<T7>, Field<T8>, Field<T9>, Field<T10>, Field<T11>, Field<T12>, Field<T13>, Field<T14>, Field<T15>, Field<T16>, Field<T17>, Field<T18>, Field<T19>, Field<T20>, Field<T21>, Field<T22>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DefaultDSLContext.mergeInto(Table)
org.jooq.impl.DSL.createOrReplaceView(String, Function<? super Field<?>, ? extends String>)	- 3.14.0 - [#10156] - These methods will be removed without replacement from a future jOOQ. They offer convenience that is unidiomatic for jOOQ's DSL, without offering functionality that would not be possible otherwise - yet they add complexity in jOOQ's internals.
org.jooq.impl.DSL.createOrReplaceView(Name, Function<? super Field<?>, ? extends Name>)	- 3.14.0 - [#10156] - These methods will be removed without replacement from a future jOOQ. They offer convenience that is unidiomatic for jOOQ's DSL, without offering functionality that would not be possible otherwise - yet they add complexity in jOOQ's internals.
org.jooq.impl.DSL.createOrReplaceView(Table<?>, Function<? super Field<?>, ? extends Field<?>>)	- 3.14.0 - [#10156] - These methods will be removed without replacement from a future jOOQ. They offer convenience that is unidiomatic for jOOQ's DSL, without offering functionality that would not be possible otherwise - yet they add complexity in jOOQ's internals.
org.jooq.impl.DSL.createView(String, Function<? super Field<?>, ? extends String>)	- 3.14.0 - [#10156] - These methods will be removed without replacement from a future jOOQ. They offer convenience that is unidiomatic for jOOQ's DSL, without offering functionality that would not be possible otherwise - yet they add complexity in jOOQ's internals.
org.jooq.impl.DSL.createView(Name, Function<? super Field<?>, ? extends Name>)	- 3.14.0 - [#10156] - These methods will be removed without replacement from a future jOOQ. They offer convenience that is unidiomatic for jOOQ's DSL, without offering functionality that would not be possible otherwise - yet they add complexity in jOOQ's internals.
org.jooq.impl.DSL.createView(Table<?>, Function<? super Field<?>, ? extends Field<?>>)	- 3.14.0 - [#10156] - These methods will be removed without replacement from a future jOOQ. They offer convenience that is unidiomatic for jOOQ's DSL, without offering functionality that would not be possible otherwise - yet they add complexity in jOOQ's internals.
org.jooq.impl.DSL.createViewIfNotExists(String, Function<? super Field<?>, ? extends String>)	- 3.14.0 - [#10156] - These methods will be removed without replacement from a future jOOQ. They offer convenience that is unidiomatic for jOOQ's DSL, without offering functionality that would not be possible otherwise - yet they add complexity in jOOQ's internals.
org.jooq.impl.DSL.createViewIfNotExists(Name, Function<? super Field<?>, ? extends Name>)	- 3.14.0 - [#10156] - These methods will be removed without replacement from a future jOOQ. They offer convenience that is unidiomatic for jOOQ's DSL, without offering functionality that would not be possible otherwise - yet they add complexity in jOOQ's internals.
org.jooq.impl.DSL.createViewIfNotExists(Table<?>, Function<? super Field<?>, ? extends Field<?>>)	- 3.14.0 - [#10156] - These methods will be removed without replacement from a future jOOQ. They offer convenience that is unidiomatic for jOOQ's DSL, without offering functionality that would not be possible otherwise - yet they add complexity in jOOQ's internals.
org.jooq.impl.DSL.getDataType(Class<T>)	- 3.11.0 - [#7483] - The (indirect) use of the internal static data type registry is not recommended.
org.jooq.impl.DSL.groupConcat(Field<?>, String)	- [#7956] - 3.12.0 - Use DSL.groupConcat(Field) and GroupConcatSeparatorStep.separator(String) instead.
org.jooq.impl.DSL.mergeInto(Table<R>, Collection<? extends Field<?>>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSL.mergeInto(Table)
org.jooq.impl.DSL.mergeInto(Table<R>, Field<?>...)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSL.mergeInto(Table)
org.jooq.impl.DSL.mergeInto(Table<R>, Field<T1>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSL.mergeInto(Table)
org.jooq.impl.DSL.mergeInto(Table<R>, Field<T1>, Field<T2>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSL.mergeInto(Table)
org.jooq.impl.DSL.mergeInto(Table<R>, Field<T1>, Field<T2>, Field<T3>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSL.mergeInto(Table)
org.jooq.impl.DSL.mergeInto(Table<R>, Field<T1>, Field<T2>, Field<T3>, Field<T4>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSL.mergeInto(Table)
org.jooq.impl.DSL.mergeInto(Table<R>, Field<T1>, Field<T2>, Field<T3>, Field<T4>, Field<T5>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSL.mergeInto(Table)
org.jooq.impl.DSL.mergeInto(Table<R>, Field<T1>, Field<T2>, Field<T3>, Field<T4>, Field<T5>, Field<T6>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSL.mergeInto(Table)
org.jooq.impl.DSL.mergeInto(Table<R>, Field<T1>, Field<T2>, Field<T3>, Field<T4>, Field<T5>, Field<T6>, Field<T7>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSL.mergeInto(Table)
org.jooq.impl.DSL.mergeInto(Table<R>, Field<T1>, Field<T2>, Field<T3>, Field<T4>, Field<T5>, Field<T6>, Field<T7>, Field<T8>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSL.mergeInto(Table)
org.jooq.impl.DSL.mergeInto(Table<R>, Field<T1>, Field<T2>, Field<T3>, Field<T4>, Field<T5>, Field<T6>, Field<T7>, Field<T8>, Field<T9>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSL.mergeInto(Table)
org.jooq.impl.DSL.mergeInto(Table<R>, Field<T1>, Field<T2>, Field<T3>, Field<T4>, Field<T5>, Field<T6>, Field<T7>, Field<T8>, Field<T9>, Field<T10>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSL.mergeInto(Table)
org.jooq.impl.DSL.mergeInto(Table<R>, Field<T1>, Field<T2>, Field<T3>, Field<T4>, Field<T5>, Field<T6>, Field<T7>, Field<T8>, Field<T9>, Field<T10>, Field<T11>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSL.mergeInto(Table)
org.jooq.impl.DSL.mergeInto(Table<R>, Field<T1>, Field<T2>, Field<T3>, Field<T4>, Field<T5>, Field<T6>, Field<T7>, Field<T8>, Field<T9>, Field<T10>, Field<T11>, Field<T12>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSL.mergeInto(Table)
org.jooq.impl.DSL.mergeInto(Table<R>, Field<T1>, Field<T2>, Field<T3>, Field<T4>, Field<T5>, Field<T6>, Field<T7>, Field<T8>, Field<T9>, Field<T10>, Field<T11>, Field<T12>, Field<T13>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSL.mergeInto(Table)
org.jooq.impl.DSL.mergeInto(Table<R>, Field<T1>, Field<T2>, Field<T3>, Field<T4>, Field<T5>, Field<T6>, Field<T7>, Field<T8>, Field<T9>, Field<T10>, Field<T11>, Field<T12>, Field<T13>, Field<T14>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSL.mergeInto(Table)
org.jooq.impl.DSL.mergeInto(Table<R>, Field<T1>, Field<T2>, Field<T3>, Field<T4>, Field<T5>, Field<T6>, Field<T7>, Field<T8>, Field<T9>, Field<T10>, Field<T11>, Field<T12>, Field<T13>, Field<T14>, Field<T15>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSL.mergeInto(Table)
org.jooq.impl.DSL.mergeInto(Table<R>, Field<T1>, Field<T2>, Field<T3>, Field<T4>, Field<T5>, Field<T6>, Field<T7>, Field<T8>, Field<T9>, Field<T10>, Field<T11>, Field<T12>, Field<T13>, Field<T14>, Field<T15>, Field<T16>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSL.mergeInto(Table)
org.jooq.impl.DSL.mergeInto(Table<R>, Field<T1>, Field<T2>, Field<T3>, Field<T4>, Field<T5>, Field<T6>, Field<T7>, Field<T8>, Field<T9>, Field<T10>, Field<T11>, Field<T12>, Field<T13>, Field<T14>, Field<T15>, Field<T16>, Field<T17>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSL.mergeInto(Table)
org.jooq.impl.DSL.mergeInto(Table<R>, Field<T1>, Field<T2>, Field<T3>, Field<T4>, Field<T5>, Field<T6>, Field<T7>, Field<T8>, Field<T9>, Field<T10>, Field<T11>, Field<T12>, Field<T13>, Field<T14>, Field<T15>, Field<T16>, Field<T17>, Field<T18>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSL.mergeInto(Table)
org.jooq.impl.DSL.mergeInto(Table<R>, Field<T1>, Field<T2>, Field<T3>, Field<T4>, Field<T5>, Field<T6>, Field<T7>, Field<T8>, Field<T9>, Field<T10>, Field<T11>, Field<T12>, Field<T13>, Field<T14>, Field<T15>, Field<T16>, Field<T17>, Field<T18>, Field<T19>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSL.mergeInto(Table)
org.jooq.impl.DSL.mergeInto(Table<R>, Field<T1>, Field<T2>, Field<T3>, Field<T4>, Field<T5>, Field<T6>, Field<T7>, Field<T8>, Field<T9>, Field<T10>, Field<T11>, Field<T12>, Field<T13>, Field<T14>, Field<T15>, Field<T16>, Field<T17>, Field<T18>, Field<T19>, Field<T20>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSL.mergeInto(Table)
org.jooq.impl.DSL.mergeInto(Table<R>, Field<T1>, Field<T2>, Field<T3>, Field<T4>, Field<T5>, Field<T6>, Field<T7>, Field<T8>, Field<T9>, Field<T10>, Field<T11>, Field<T12>, Field<T13>, Field<T14>, Field<T15>, Field<T16>, Field<T17>, Field<T18>, Field<T19>, Field<T20>, Field<T21>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSL.mergeInto(Table)
org.jooq.impl.DSL.mergeInto(Table<R>, Field<T1>, Field<T2>, Field<T3>, Field<T4>, Field<T5>, Field<T6>, Field<T7>, Field<T8>, Field<T9>, Field<T10>, Field<T11>, Field<T12>, Field<T13>, Field<T14>, Field<T15>, Field<T16>, Field<T17>, Field<T18>, Field<T19>, Field<T20>, Field<T21>, Field<T22>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSL.mergeInto(Table)
org.jooq.impl.DSL.nullSafe(Field<?>...)	- [#11092] - 3.15.0 - This method will be removed without public replacement.
org.jooq.impl.DSL.nullSafe(Field<?>[], DataType<?>)	- [#11092] - 3.15.0 - This method will be removed without public replacement.
org.jooq.impl.DSL.nullSafe(Field<T>)	- [#11092] - 3.15.0 - This method will be removed without public replacement.
org.jooq.impl.DSL.nullSafe(Field<T>, DataType<?>)	- [#11092] - 3.15.0 - This method will be removed without public replacement.
org.jooq.impl.DSL.nullSafeDataType(Field<T>)	- [#11092] - 3.15.0 - This method will be removed without public replacement.
org.jooq.impl.DSL.nullSafeList(Field<?>...)	- [#11092] - 3.15.0 - This method will be removed without public replacement.
org.jooq.impl.DSL.nullSafeList(Field<?>[], DataType<?>)	- [#11092] - 3.15.0 - This method will be removed without public replacement.
org.jooq.impl.DSL.rowField(Row1<T1>)	- [#11812] - 3.15.0 - Use Row1 as a SelectField directly, instead.
org.jooq.impl.DSL.rowField(Row10<T1, T2, T3, T4, T5, T6, T7, T8, T9, T10>)	- [#11812] - 3.15.0 - Use Row10 as a SelectField directly, instead.
org.jooq.impl.DSL.rowField(Row11<T1, T2, T3, T4, T5, T6, T7, T8, T9, T10, T11>)	- [#11812] - 3.15.0 - Use Row11 as a SelectField directly, instead.
org.jooq.impl.DSL.rowField(Row12<T1, T2, T3, T4, T5, T6, T7, T8, T9, T10, T11, T12>)	- [#11812] - 3.15.0 - Use Row12 as a SelectField directly, instead.
org.jooq.impl.DSL.rowField(Row13<T1, T2, T3, T4, T5, T6, T7, T8, T9, T10, T11, T12, T13>)	- [#11812] - 3.15.0 - Use Row13 as a SelectField directly, instead.
org.jooq.impl.DSL.rowField(Row14<T1, T2, T3, T4, T5, T6, T7, T8, T9, T10, T11, T12, T13, T14>)	- [#11812] - 3.15.0 - Use Row14 as a SelectField directly, instead.
org.jooq.impl.DSL.rowField(Row15<T1, T2, T3, T4, T5, T6, T7, T8, T9, T10, T11, T12, T13, T14, T15>)	- [#11812] - 3.15.0 - Use Row15 as a SelectField directly, instead.
org.jooq.impl.DSL.rowField(Row16<T1, T2, T3, T4, T5, T6, T7, T8, T9, T10, T11, T12, T13, T14, T15, T16>)	- [#11812] - 3.15.0 - Use Row16 as a SelectField directly, instead.
org.jooq.impl.DSL.rowField(Row17<T1, T2, T3, T4, T5, T6, T7, T8, T9, T10, T11, T12, T13, T14, T15, T16, T17>)	- [#11812] - 3.15.0 - Use Row17 as a SelectField directly, instead.
org.jooq.impl.DSL.rowField(Row18<T1, T2, T3, T4, T5, T6, T7, T8, T9, T10, T11, T12, T13, T14, T15, T16, T17, T18>)	- [#11812] - 3.15.0 - Use Row18 as a SelectField directly, instead.
org.jooq.impl.DSL.rowField(Row19<T1, T2, T3, T4, T5, T6, T7, T8, T9, T10, T11, T12, T13, T14, T15, T16, T17, T18, T19>)	- [#11812] - 3.15.0 - Use Row19 as a SelectField directly, instead.
org.jooq.impl.DSL.rowField(Row2<T1, T2>)	- [#11812] - 3.15.0 - Use Row2 as a SelectField directly, instead.
org.jooq.impl.DSL.rowField(Row20<T1, T2, T3, T4, T5, T6, T7, T8, T9, T10, T11, T12, T13, T14, T15, T16, T17, T18, T19, T20>)	- [#11812] - 3.15.0 - Use Row20 as a SelectField directly, instead.
org.jooq.impl.DSL.rowField(Row21<T1, T2, T3, T4, T5, T6, T7, T8, T9, T10, T11, T12, T13, T14, T15, T16, T17, T18, T19, T20, T21>)	- [#11812] - 3.15.0 - Use Row21 as a SelectField directly, instead.
org.jooq.impl.DSL.rowField(Row22<T1, T2, T3, T4, T5, T6, T7, T8, T9, T10, T11, T12, T13, T14, T15, T16, T17, T18, T19, T20, T21, T22>)	- [#11812] - 3.15.0 - Use Row22 as a SelectField directly, instead.
org.jooq.impl.DSL.rowField(Row3<T1, T2, T3>)	- [#11812] - 3.15.0 - Use Row3 as a SelectField directly, instead.
org.jooq.impl.DSL.rowField(Row4<T1, T2, T3, T4>)	- [#11812] - 3.15.0 - Use Row4 as a SelectField directly, instead.
org.jooq.impl.DSL.rowField(Row5<T1, T2, T3, T4, T5>)	- [#11812] - 3.15.0 - Use Row5 as a SelectField directly, instead.
org.jooq.impl.DSL.rowField(Row6<T1, T2, T3, T4, T5, T6>)	- [#11812] - 3.15.0 - Use Row6 as a SelectField directly, instead.
org.jooq.impl.DSL.rowField(Row7<T1, T2, T3, T4, T5, T6, T7>)	- [#11812] - 3.15.0 - Use Row7 as a SelectField directly, instead.
org.jooq.impl.DSL.rowField(Row8<T1, T2, T3, T4, T5, T6, T7, T8>)	- [#11812] - 3.15.0 - Use Row8 as a SelectField directly, instead.
org.jooq.impl.DSL.rowField(Row9<T1, T2, T3, T4, T5, T6, T7, T8, T9>)	- [#11812] - 3.15.0 - Use Row9 as a SelectField directly, instead.
org.jooq.impl.DSL.rowField(RowN)	- [#11812] - 3.15.0 - Use RowN as a SelectField directly, instead.
org.jooq.impl.DSL.sequence(String)	- 3.10 - [#6162] - Use DSL.sequence(Name) instead.
org.jooq.impl.DSL.sequence(String, Class<T>)	- 3.10 - [#6162] - Use DSL.sequence(Name, Class) instead.
org.jooq.impl.DSL.sequence(String, DataType<T>)	- 3.10 - [#6162] - Use DSL.sequence(Name, DataType) instead.
org.jooq.impl.DSL.with(String, Function<? super Field<?>, ? extends String>)	- 3.14.0 - [#10156] - These methods will be removed without replacement from a future jOOQ. They offer convenience that is unidiomatic for jOOQ's DSL, without offering functionality that would not be possible otherwise - yet they add complexity in jOOQ's internals.
org.jooq.impl.DSL.withRecursive(String, Function<? super Field<?>, ? extends String>)	- 3.14.0 - [#10156] - These methods will be removed without replacement from a future jOOQ. They offer convenience that is unidiomatic for jOOQ's DSL, without offering functionality that would not be possible otherwise - yet they add complexity in jOOQ's internals.
org.jooq.impl.Internal.createForeignKey(UniqueKey<U>, Table<R>, String, TableField<R, ?>...)	- 3.14.0 - [#9404] - Please re-generate your code.
org.jooq.impl.Internal.createForeignKey(UniqueKey<U>, Table<R>, String, TableField<R, ?>[], boolean)	- 3.14.0 - [#9404] - Please re-generate your code.
org.jooq.impl.Internal.createForeignKey(UniqueKey<U>, Table<R>, TableField<R, ?>...)	- 3.14.0 - [#9404] - Please re-generate your code.
org.jooq.impl.Internal.createIndex(String, Table<?>, OrderField<?>[], boolean)	- 3.14.0 - [#9404] - Please re-generate your code.
org.jooq.impl.Internal.createUniqueKey(Table<R>, String, TableField<R, ?>...)	- 3.14.0 - [#9404] - Please re-generate your code.
org.jooq.impl.Internal.createUniqueKey(Table<R>, String, TableField<R, ?>[], boolean)	- 3.14.0 - [#9404] - Please re-generate your code.
org.jooq.impl.Internal.fields(TableField<R, ER>)	- [#11058] - 3.14.5 - Please re-generate your code.
org.jooq.impl.Internal.fieldsRow(TableField<R, ER>)	- [#12238] - 3.16.0 - Please re-generate your code.
org.jooq.impl.UDTImpl.createField(String, DataType<T>, UDT<R>)	- 3.12.0 - [#8000] - Use UDTImpl.createField(Name, DataType, UDT) instead.
org.jooq.impl.UDTImpl.createField(String, DataType<T>, UDT<R>, String)	- 3.12.0 - [#8000] - Use UDTImpl.createField(Name, DataType, UDT, String) instead.
org.jooq.impl.UDTImpl.createField(String, DataType<T>, UDT<R>, String, Binding<T, U>)	- 3.12.0 - [#8000] - Use UDTImpl.createField(Name, DataType, UDT, String, Binding) instead.
org.jooq.impl.UDTImpl.createField(String, DataType<T>, UDT<R>, String, Converter<T, U>)	- 3.12.0 - [#8000] - Use UDTImpl.createField(Name, DataType, UDT, String, Converter) instead.
org.jooq.impl.UDTImpl.createField(String, DataType<T>, UDT<R>, String, Converter<X, U>, Binding<T, X>)	- 3.12.0 - [#8000] - Use UDTImpl.createField(Name, DataType, UDT, String, Converter, Binding) instead.
org.jooq.LoaderCSVStep.fieldsFromSource()	- 3.14.0 - [#10010] - Use LoaderCSVStep.fieldsCorresponding() instead.
org.jooq.LoaderJSONOptionsStep.ignoreRows(int)	- [#4859] - This is not supported for JSON loading.
org.jooq.LoaderJSONStep.fieldsFromSource()	- 3.14.0 - [#10010] - Use LoaderJSONStep.fieldsCorresponding() instead.
org.jooq.LoaderListenerStep.onRow(LoaderRowListener)	- 3.14.0 - [#4941] - Use LoaderListenerStep.onRowEnd(LoaderRowListener) instead.
org.jooq.LoaderRowsStep.fieldsFromSource()	- 3.14.0 - [#10010] - Use LoaderRowsStep.fieldsCorresponding() instead.
org.jooq.MergeKeyStep1.key(Collection<? extends Field<?>>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeKeyStep1.key(Field<?>...)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeKeyStep10.key(Collection<? extends Field<?>>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeKeyStep10.key(Field<?>...)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeKeyStep11.key(Collection<? extends Field<?>>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeKeyStep11.key(Field<?>...)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeKeyStep12.key(Collection<? extends Field<?>>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeKeyStep12.key(Field<?>...)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeKeyStep13.key(Collection<? extends Field<?>>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeKeyStep13.key(Field<?>...)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeKeyStep14.key(Collection<? extends Field<?>>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeKeyStep14.key(Field<?>...)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeKeyStep15.key(Collection<? extends Field<?>>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeKeyStep15.key(Field<?>...)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeKeyStep16.key(Collection<? extends Field<?>>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeKeyStep16.key(Field<?>...)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeKeyStep17.key(Collection<? extends Field<?>>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeKeyStep17.key(Field<?>...)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeKeyStep18.key(Collection<? extends Field<?>>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeKeyStep18.key(Field<?>...)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeKeyStep19.key(Collection<? extends Field<?>>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeKeyStep19.key(Field<?>...)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeKeyStep2.key(Collection<? extends Field<?>>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeKeyStep2.key(Field<?>...)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeKeyStep20.key(Collection<? extends Field<?>>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeKeyStep20.key(Field<?>...)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeKeyStep21.key(Collection<? extends Field<?>>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeKeyStep21.key(Field<?>...)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeKeyStep22.key(Collection<? extends Field<?>>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeKeyStep22.key(Field<?>...)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeKeyStep3.key(Collection<? extends Field<?>>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeKeyStep3.key(Field<?>...)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeKeyStep4.key(Collection<? extends Field<?>>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeKeyStep4.key(Field<?>...)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeKeyStep5.key(Collection<? extends Field<?>>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeKeyStep5.key(Field<?>...)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeKeyStep6.key(Collection<? extends Field<?>>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeKeyStep6.key(Field<?>...)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeKeyStep7.key(Collection<? extends Field<?>>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeKeyStep7.key(Field<?>...)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeKeyStep8.key(Collection<? extends Field<?>>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeKeyStep8.key(Field<?>...)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeKeyStep9.key(Collection<? extends Field<?>>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeKeyStep9.key(Field<?>...)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeUsingStep.columns(Collection<? extends Field<?>>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeUsingStep.columns(Field<?>...)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeUsingStep.columns(Field<T1>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeUsingStep.columns(Field<T1>, Field<T2>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeUsingStep.columns(Field<T1>, Field<T2>, Field<T3>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeUsingStep.columns(Field<T1>, Field<T2>, Field<T3>, Field<T4>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeUsingStep.columns(Field<T1>, Field<T2>, Field<T3>, Field<T4>, Field<T5>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeUsingStep.columns(Field<T1>, Field<T2>, Field<T3>, Field<T4>, Field<T5>, Field<T6>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeUsingStep.columns(Field<T1>, Field<T2>, Field<T3>, Field<T4>, Field<T5>, Field<T6>, Field<T7>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeUsingStep.columns(Field<T1>, Field<T2>, Field<T3>, Field<T4>, Field<T5>, Field<T6>, Field<T7>, Field<T8>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeUsingStep.columns(Field<T1>, Field<T2>, Field<T3>, Field<T4>, Field<T5>, Field<T6>, Field<T7>, Field<T8>, Field<T9>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeUsingStep.columns(Field<T1>, Field<T2>, Field<T3>, Field<T4>, Field<T5>, Field<T6>, Field<T7>, Field<T8>, Field<T9>, Field<T10>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeUsingStep.columns(Field<T1>, Field<T2>, Field<T3>, Field<T4>, Field<T5>, Field<T6>, Field<T7>, Field<T8>, Field<T9>, Field<T10>, Field<T11>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeUsingStep.columns(Field<T1>, Field<T2>, Field<T3>, Field<T4>, Field<T5>, Field<T6>, Field<T7>, Field<T8>, Field<T9>, Field<T10>, Field<T11>, Field<T12>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeUsingStep.columns(Field<T1>, Field<T2>, Field<T3>, Field<T4>, Field<T5>, Field<T6>, Field<T7>, Field<T8>, Field<T9>, Field<T10>, Field<T11>, Field<T12>, Field<T13>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeUsingStep.columns(Field<T1>, Field<T2>, Field<T3>, Field<T4>, Field<T5>, Field<T6>, Field<T7>, Field<T8>, Field<T9>, Field<T10>, Field<T11>, Field<T12>, Field<T13>, Field<T14>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeUsingStep.columns(Field<T1>, Field<T2>, Field<T3>, Field<T4>, Field<T5>, Field<T6>, Field<T7>, Field<T8>, Field<T9>, Field<T10>, Field<T11>, Field<T12>, Field<T13>, Field<T14>, Field<T15>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeUsingStep.columns(Field<T1>, Field<T2>, Field<T3>, Field<T4>, Field<T5>, Field<T6>, Field<T7>, Field<T8>, Field<T9>, Field<T10>, Field<T11>, Field<T12>, Field<T13>, Field<T14>, Field<T15>, Field<T16>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeUsingStep.columns(Field<T1>, Field<T2>, Field<T3>, Field<T4>, Field<T5>, Field<T6>, Field<T7>, Field<T8>, Field<T9>, Field<T10>, Field<T11>, Field<T12>, Field<T13>, Field<T14>, Field<T15>, Field<T16>, Field<T17>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeUsingStep.columns(Field<T1>, Field<T2>, Field<T3>, Field<T4>, Field<T5>, Field<T6>, Field<T7>, Field<T8>, Field<T9>, Field<T10>, Field<T11>, Field<T12>, Field<T13>, Field<T14>, Field<T15>, Field<T16>, Field<T17>, Field<T18>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeUsingStep.columns(Field<T1>, Field<T2>, Field<T3>, Field<T4>, Field<T5>, Field<T6>, Field<T7>, Field<T8>, Field<T9>, Field<T10>, Field<T11>, Field<T12>, Field<T13>, Field<T14>, Field<T15>, Field<T16>, Field<T17>, Field<T18>, Field<T19>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeUsingStep.columns(Field<T1>, Field<T2>, Field<T3>, Field<T4>, Field<T5>, Field<T6>, Field<T7>, Field<T8>, Field<T9>, Field<T10>, Field<T11>, Field<T12>, Field<T13>, Field<T14>, Field<T15>, Field<T16>, Field<T17>, Field<T18>, Field<T19>, Field<T20>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeUsingStep.columns(Field<T1>, Field<T2>, Field<T3>, Field<T4>, Field<T5>, Field<T6>, Field<T7>, Field<T8>, Field<T9>, Field<T10>, Field<T11>, Field<T12>, Field<T13>, Field<T14>, Field<T15>, Field<T16>, Field<T17>, Field<T18>, Field<T19>, Field<T20>, Field<T21>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeUsingStep.columns(Field<T1>, Field<T2>, Field<T3>, Field<T4>, Field<T5>, Field<T6>, Field<T7>, Field<T8>, Field<T9>, Field<T10>, Field<T11>, Field<T12>, Field<T13>, Field<T14>, Field<T15>, Field<T16>, Field<T17>, Field<T18>, Field<T19>, Field<T20>, Field<T21>, Field<T22>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeValuesStep1.select(Select<? extends Record1<T1>>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeValuesStep1.values(Collection<?>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeValuesStep1.values(Field<T1>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeValuesStep1.values(T1)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeValuesStep10.select(Select<? extends Record10<T1, T2, T3, T4, T5, T6, T7, T8, T9, T10>>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeValuesStep10.values(Collection<?>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeValuesStep10.values(Field<T1>, Field<T2>, Field<T3>, Field<T4>, Field<T5>, Field<T6>, Field<T7>, Field<T8>, Field<T9>, Field<T10>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeValuesStep10.values(T1, T2, T3, T4, T5, T6, T7, T8, T9, T10)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeValuesStep11.select(Select<? extends Record11<T1, T2, T3, T4, T5, T6, T7, T8, T9, T10, T11>>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeValuesStep11.values(Collection<?>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeValuesStep11.values(Field<T1>, Field<T2>, Field<T3>, Field<T4>, Field<T5>, Field<T6>, Field<T7>, Field<T8>, Field<T9>, Field<T10>, Field<T11>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeValuesStep11.values(T1, T2, T3, T4, T5, T6, T7, T8, T9, T10, T11)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeValuesStep12.select(Select<? extends Record12<T1, T2, T3, T4, T5, T6, T7, T8, T9, T10, T11, T12>>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeValuesStep12.values(Collection<?>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeValuesStep12.values(Field<T1>, Field<T2>, Field<T3>, Field<T4>, Field<T5>, Field<T6>, Field<T7>, Field<T8>, Field<T9>, Field<T10>, Field<T11>, Field<T12>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeValuesStep12.values(T1, T2, T3, T4, T5, T6, T7, T8, T9, T10, T11, T12)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeValuesStep13.select(Select<? extends Record13<T1, T2, T3, T4, T5, T6, T7, T8, T9, T10, T11, T12, T13>>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeValuesStep13.values(Collection<?>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeValuesStep13.values(Field<T1>, Field<T2>, Field<T3>, Field<T4>, Field<T5>, Field<T6>, Field<T7>, Field<T8>, Field<T9>, Field<T10>, Field<T11>, Field<T12>, Field<T13>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeValuesStep13.values(T1, T2, T3, T4, T5, T6, T7, T8, T9, T10, T11, T12, T13)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeValuesStep14.select(Select<? extends Record14<T1, T2, T3, T4, T5, T6, T7, T8, T9, T10, T11, T12, T13, T14>>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeValuesStep14.values(Collection<?>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeValuesStep14.values(Field<T1>, Field<T2>, Field<T3>, Field<T4>, Field<T5>, Field<T6>, Field<T7>, Field<T8>, Field<T9>, Field<T10>, Field<T11>, Field<T12>, Field<T13>, Field<T14>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeValuesStep14.values(T1, T2, T3, T4, T5, T6, T7, T8, T9, T10, T11, T12, T13, T14)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeValuesStep15.select(Select<? extends Record15<T1, T2, T3, T4, T5, T6, T7, T8, T9, T10, T11, T12, T13, T14, T15>>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeValuesStep15.values(Collection<?>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeValuesStep15.values(Field<T1>, Field<T2>, Field<T3>, Field<T4>, Field<T5>, Field<T6>, Field<T7>, Field<T8>, Field<T9>, Field<T10>, Field<T11>, Field<T12>, Field<T13>, Field<T14>, Field<T15>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeValuesStep15.values(T1, T2, T3, T4, T5, T6, T7, T8, T9, T10, T11, T12, T13, T14, T15)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeValuesStep16.select(Select<? extends Record16<T1, T2, T3, T4, T5, T6, T7, T8, T9, T10, T11, T12, T13, T14, T15, T16>>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeValuesStep16.values(Collection<?>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeValuesStep16.values(Field<T1>, Field<T2>, Field<T3>, Field<T4>, Field<T5>, Field<T6>, Field<T7>, Field<T8>, Field<T9>, Field<T10>, Field<T11>, Field<T12>, Field<T13>, Field<T14>, Field<T15>, Field<T16>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeValuesStep16.values(T1, T2, T3, T4, T5, T6, T7, T8, T9, T10, T11, T12, T13, T14, T15, T16)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeValuesStep17.select(Select<? extends Record17<T1, T2, T3, T4, T5, T6, T7, T8, T9, T10, T11, T12, T13, T14, T15, T16, T17>>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeValuesStep17.values(Collection<?>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeValuesStep17.values(Field<T1>, Field<T2>, Field<T3>, Field<T4>, Field<T5>, Field<T6>, Field<T7>, Field<T8>, Field<T9>, Field<T10>, Field<T11>, Field<T12>, Field<T13>, Field<T14>, Field<T15>, Field<T16>, Field<T17>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeValuesStep17.values(T1, T2, T3, T4, T5, T6, T7, T8, T9, T10, T11, T12, T13, T14, T15, T16, T17)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeValuesStep18.select(Select<? extends Record18<T1, T2, T3, T4, T5, T6, T7, T8, T9, T10, T11, T12, T13, T14, T15, T16, T17, T18>>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeValuesStep18.values(Collection<?>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeValuesStep18.values(Field<T1>, Field<T2>, Field<T3>, Field<T4>, Field<T5>, Field<T6>, Field<T7>, Field<T8>, Field<T9>, Field<T10>, Field<T11>, Field<T12>, Field<T13>, Field<T14>, Field<T15>, Field<T16>, Field<T17>, Field<T18>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeValuesStep18.values(T1, T2, T3, T4, T5, T6, T7, T8, T9, T10, T11, T12, T13, T14, T15, T16, T17, T18)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeValuesStep19.select(Select<? extends Record19<T1, T2, T3, T4, T5, T6, T7, T8, T9, T10, T11, T12, T13, T14, T15, T16, T17, T18, T19>>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeValuesStep19.values(Collection<?>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeValuesStep19.values(Field<T1>, Field<T2>, Field<T3>, Field<T4>, Field<T5>, Field<T6>, Field<T7>, Field<T8>, Field<T9>, Field<T10>, Field<T11>, Field<T12>, Field<T13>, Field<T14>, Field<T15>, Field<T16>, Field<T17>, Field<T18>, Field<T19>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeValuesStep19.values(T1, T2, T3, T4, T5, T6, T7, T8, T9, T10, T11, T12, T13, T14, T15, T16, T17, T18, T19)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeValuesStep2.select(Select<? extends Record2<T1, T2>>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeValuesStep2.values(Collection<?>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeValuesStep2.values(Field<T1>, Field<T2>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeValuesStep2.values(T1, T2)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeValuesStep20.select(Select<? extends Record20<T1, T2, T3, T4, T5, T6, T7, T8, T9, T10, T11, T12, T13, T14, T15, T16, T17, T18, T19, T20>>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeValuesStep20.values(Collection<?>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeValuesStep20.values(Field<T1>, Field<T2>, Field<T3>, Field<T4>, Field<T5>, Field<T6>, Field<T7>, Field<T8>, Field<T9>, Field<T10>, Field<T11>, Field<T12>, Field<T13>, Field<T14>, Field<T15>, Field<T16>, Field<T17>, Field<T18>, Field<T19>, Field<T20>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeValuesStep20.values(T1, T2, T3, T4, T5, T6, T7, T8, T9, T10, T11, T12, T13, T14, T15, T16, T17, T18, T19, T20)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeValuesStep21.select(Select<? extends Record21<T1, T2, T3, T4, T5, T6, T7, T8, T9, T10, T11, T12, T13, T14, T15, T16, T17, T18, T19, T20, T21>>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeValuesStep21.values(Collection<?>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeValuesStep21.values(Field<T1>, Field<T2>, Field<T3>, Field<T4>, Field<T5>, Field<T6>, Field<T7>, Field<T8>, Field<T9>, Field<T10>, Field<T11>, Field<T12>, Field<T13>, Field<T14>, Field<T15>, Field<T16>, Field<T17>, Field<T18>, Field<T19>, Field<T20>, Field<T21>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeValuesStep21.values(T1, T2, T3, T4, T5, T6, T7, T8, T9, T10, T11, T12, T13, T14, T15, T16, T17, T18, T19, T20, T21)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeValuesStep22.select(Select<? extends Record22<T1, T2, T3, T4, T5, T6, T7, T8, T9, T10, T11, T12, T13, T14, T15, T16, T17, T18, T19, T20, T21, T22>>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeValuesStep22.values(Collection<?>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeValuesStep22.values(Field<T1>, Field<T2>, Field<T3>, Field<T4>, Field<T5>, Field<T6>, Field<T7>, Field<T8>, Field<T9>, Field<T10>, Field<T11>, Field<T12>, Field<T13>, Field<T14>, Field<T15>, Field<T16>, Field<T17>, Field<T18>, Field<T19>, Field<T20>, Field<T21>, Field<T22>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeValuesStep22.values(T1, T2, T3, T4, T5, T6, T7, T8, T9, T10, T11, T12, T13, T14, T15, T16, T17, T18, T19, T20, T21, T22)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeValuesStep3.select(Select<? extends Record3<T1, T2, T3>>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeValuesStep3.values(Collection<?>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeValuesStep3.values(Field<T1>, Field<T2>, Field<T3>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeValuesStep3.values(T1, T2, T3)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeValuesStep4.select(Select<? extends Record4<T1, T2, T3, T4>>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeValuesStep4.values(Collection<?>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeValuesStep4.values(Field<T1>, Field<T2>, Field<T3>, Field<T4>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeValuesStep4.values(T1, T2, T3, T4)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeValuesStep5.select(Select<? extends Record5<T1, T2, T3, T4, T5>>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeValuesStep5.values(Collection<?>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeValuesStep5.values(Field<T1>, Field<T2>, Field<T3>, Field<T4>, Field<T5>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeValuesStep5.values(T1, T2, T3, T4, T5)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeValuesStep6.select(Select<? extends Record6<T1, T2, T3, T4, T5, T6>>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeValuesStep6.values(Collection<?>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeValuesStep6.values(Field<T1>, Field<T2>, Field<T3>, Field<T4>, Field<T5>, Field<T6>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeValuesStep6.values(T1, T2, T3, T4, T5, T6)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeValuesStep7.select(Select<? extends Record7<T1, T2, T3, T4, T5, T6, T7>>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeValuesStep7.values(Collection<?>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeValuesStep7.values(Field<T1>, Field<T2>, Field<T3>, Field<T4>, Field<T5>, Field<T6>, Field<T7>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeValuesStep7.values(T1, T2, T3, T4, T5, T6, T7)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeValuesStep8.select(Select<? extends Record8<T1, T2, T3, T4, T5, T6, T7, T8>>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeValuesStep8.values(Collection<?>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeValuesStep8.values(Field<T1>, Field<T2>, Field<T3>, Field<T4>, Field<T5>, Field<T6>, Field<T7>, Field<T8>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeValuesStep8.values(T1, T2, T3, T4, T5, T6, T7, T8)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeValuesStep9.select(Select<? extends Record9<T1, T2, T3, T4, T5, T6, T7, T8, T9>>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeValuesStep9.values(Collection<?>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeValuesStep9.values(Field<T1>, Field<T2>, Field<T3>, Field<T4>, Field<T5>, Field<T6>, Field<T7>, Field<T8>, Field<T9>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.MergeValuesStep9.values(T1, T2, T3, T4, T5, T6, T7, T8, T9)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via DSLContext.mergeInto(Table)
org.jooq.Name.fields(BiFunction<? super Field<?>, ? super Integer, ? extends String>)	- 3.14.0 - [#10156] - These methods will be removed without replacement from a future jOOQ. They offer convenience that is unidiomatic for jOOQ's DSL, without offering functionality that would not be possible otherwise - yet they add complexity in jOOQ's internals.
org.jooq.Name.fields(Function<? super Field<?>, ? extends String>)	- 3.14.0 - [#10156] - These methods will be removed without replacement from a future jOOQ. They offer convenience that is unidiomatic for jOOQ's DSL, without offering functionality that would not be possible otherwise - yet they add complexity in jOOQ's internals.
org.jooq.Param.setConverted(Object)	- 3.8.0 - [#4991] In jOOQ 4.0, Param will be made immutable. Modifying Param values is strongly discouraged.
org.jooq.Param.setInline(boolean)	- 3.8.0 - [#4991] In jOOQ 4.0, Param will be made immutable. Modifying Param values is strongly discouraged.
org.jooq.Param.setValue(T)	- 3.8.0 - [#4991] In jOOQ 4.0, Param will be made immutable. Modifying Param values is strongly discouraged.
org.jooq.PivotForStep.on(Field<T>)	- 3.12.0 - [#8163] - Use PivotForStep.for_(Field) instead.
org.jooq.Queries.stream()	- 3.10 - [#6143] - Use Queries.queryStream() instead.
org.jooq.QueryPartInternal.accept(Context<?>)	- Calling QueryPartInternal.accept(Context) directly on a QueryPart is almost always a mistake. Instead, Context.visit(QueryPart) should be called.
org.jooq.QueryPartInternal.rendersContent(Context<?>)	- Calling QueryPartInternal.rendersContent(Context) directly on a QueryPart is almost always a mistake.
org.jooq.Result.intern(int...)	- 3.10 - [#6254] - This functionality is no longer supported and will be removed in 4.0
org.jooq.Result.intern(String...)	- 3.10 - [#6254] - This functionality is no longer supported and will be removed in 4.0
org.jooq.Result.intern(Field<?>...)	- 3.10 - [#6254] - This functionality is no longer supported and will be removed in 4.0
org.jooq.Result.intern(Name...)	- 3.10 - [#6254] - This functionality is no longer supported and will be removed in 4.0
org.jooq.Result.into(H)	- 3.15.0 - [#11902] - Use Iterable.forEach(Consumer) based methods, instead.
org.jooq.ResultQuery.fetchInto(H)	- 3.15.0 - [#11902] - Use Iterable.forEach(Consumer) based methods, instead.
org.jooq.ResultQuery.intern(int...)	- 3.10 - [#6254] - This functionality is no longer supported and will be removed in 4.0
org.jooq.ResultQuery.intern(String...)	- 3.10 - [#6254] - This functionality is no longer supported and will be removed in 4.0
org.jooq.ResultQuery.intern(Field<?>...)	- 3.10 - [#6254] - This functionality is no longer supported and will be removed in 4.0
org.jooq.ResultQuery.intern(Name...)	- 3.10 - [#6254] - This functionality is no longer supported and will be removed in 4.0
org.jooq.SelectQuery.addSeekBefore(Collection<? extends Field<?>>)	- [#7461] - SEEK BEFORE is not implemented correctly
org.jooq.SelectQuery.addSeekBefore(Field<?>...)	- [#7461] - SEEK BEFORE is not implemented correctly
org.jooq.SelectQuery.setForUpdateNoWait()	[#5218] - 3.14.0 - Use SelectQuery.setForLockModeNoWait()
org.jooq.SelectQuery.setForUpdateOf(Collection<? extends Field<?>>)	[#5218] - 3.14.0 - Use SelectQuery.setForLockModeOf(Collection)
org.jooq.SelectQuery.setForUpdateOf(Field<?>...)	[#5218] - 3.14.0 - Use SelectQuery.setForLockModeOf(Field...)
org.jooq.SelectQuery.setForUpdateOf(Table<?>...)	[#5218] - 3.14.0 - Use SelectQuery.setForLockModeOf(Table...)
org.jooq.SelectQuery.setForUpdateSkipLocked()	[#5218] - 3.14.0 - Use SelectQuery.setForLockModeSkipLocked()
org.jooq.SelectQuery.setForUpdateWait(int)	[#5218] - 3.14.0 - Use SelectQuery.setForLockModeWait(int)
org.jooq.SelectSeekStep1.seekBefore(Field<T1>)	- [#7461] - SEEK BEFORE is not implemented correctly
org.jooq.SelectSeekStep1.seekBefore(T1)	- [#7461] - SEEK BEFORE is not implemented correctly
org.jooq.SelectSeekStep10.seekBefore(Field<T1>, Field<T2>, Field<T3>, Field<T4>, Field<T5>, Field<T6>, Field<T7>, Field<T8>, Field<T9>, Field<T10>)	- [#7461] - SEEK BEFORE is not implemented correctly
org.jooq.SelectSeekStep10.seekBefore(T1, T2, T3, T4, T5, T6, T7, T8, T9, T10)	- [#7461] - SEEK BEFORE is not implemented correctly
org.jooq.SelectSeekStep11.seekBefore(Field<T1>, Field<T2>, Field<T3>, Field<T4>, Field<T5>, Field<T6>, Field<T7>, Field<T8>, Field<T9>, Field<T10>, Field<T11>)	- [#7461] - SEEK BEFORE is not implemented correctly
org.jooq.SelectSeekStep11.seekBefore(T1, T2, T3, T4, T5, T6, T7, T8, T9, T10, T11)	- [#7461] - SEEK BEFORE is not implemented correctly
org.jooq.SelectSeekStep12.seekBefore(Field<T1>, Field<T2>, Field<T3>, Field<T4>, Field<T5>, Field<T6>, Field<T7>, Field<T8>, Field<T9>, Field<T10>, Field<T11>, Field<T12>)	- [#7461] - SEEK BEFORE is not implemented correctly
org.jooq.SelectSeekStep12.seekBefore(T1, T2, T3, T4, T5, T6, T7, T8, T9, T10, T11, T12)	- [#7461] - SEEK BEFORE is not implemented correctly
org.jooq.SelectSeekStep13.seekBefore(Field<T1>, Field<T2>, Field<T3>, Field<T4>, Field<T5>, Field<T6>, Field<T7>, Field<T8>, Field<T9>, Field<T10>, Field<T11>, Field<T12>, Field<T13>)	- [#7461] - SEEK BEFORE is not implemented correctly
org.jooq.SelectSeekStep13.seekBefore(T1, T2, T3, T4, T5, T6, T7, T8, T9, T10, T11, T12, T13)	- [#7461] - SEEK BEFORE is not implemented correctly
org.jooq.SelectSeekStep14.seekBefore(Field<T1>, Field<T2>, Field<T3>, Field<T4>, Field<T5>, Field<T6>, Field<T7>, Field<T8>, Field<T9>, Field<T10>, Field<T11>, Field<T12>, Field<T13>, Field<T14>)	- [#7461] - SEEK BEFORE is not implemented correctly
org.jooq.SelectSeekStep14.seekBefore(T1, T2, T3, T4, T5, T6, T7, T8, T9, T10, T11, T12, T13, T14)	- [#7461] - SEEK BEFORE is not implemented correctly
org.jooq.SelectSeekStep15.seekBefore(Field<T1>, Field<T2>, Field<T3>, Field<T4>, Field<T5>, Field<T6>, Field<T7>, Field<T8>, Field<T9>, Field<T10>, Field<T11>, Field<T12>, Field<T13>, Field<T14>, Field<T15>)	- [#7461] - SEEK BEFORE is not implemented correctly
org.jooq.SelectSeekStep15.seekBefore(T1, T2, T3, T4, T5, T6, T7, T8, T9, T10, T11, T12, T13, T14, T15)	- [#7461] - SEEK BEFORE is not implemented correctly
org.jooq.SelectSeekStep16.seekBefore(Field<T1>, Field<T2>, Field<T3>, Field<T4>, Field<T5>, Field<T6>, Field<T7>, Field<T8>, Field<T9>, Field<T10>, Field<T11>, Field<T12>, Field<T13>, Field<T14>, Field<T15>, Field<T16>)	- [#7461] - SEEK BEFORE is not implemented correctly
org.jooq.SelectSeekStep16.seekBefore(T1, T2, T3, T4, T5, T6, T7, T8, T9, T10, T11, T12, T13, T14, T15, T16)	- [#7461] - SEEK BEFORE is not implemented correctly
org.jooq.SelectSeekStep17.seekBefore(Field<T1>, Field<T2>, Field<T3>, Field<T4>, Field<T5>, Field<T6>, Field<T7>, Field<T8>, Field<T9>, Field<T10>, Field<T11>, Field<T12>, Field<T13>, Field<T14>, Field<T15>, Field<T16>, Field<T17>)	- [#7461] - SEEK BEFORE is not implemented correctly
org.jooq.SelectSeekStep17.seekBefore(T1, T2, T3, T4, T5, T6, T7, T8, T9, T10, T11, T12, T13, T14, T15, T16, T17)	- [#7461] - SEEK BEFORE is not implemented correctly
org.jooq.SelectSeekStep18.seekBefore(Field<T1>, Field<T2>, Field<T3>, Field<T4>, Field<T5>, Field<T6>, Field<T7>, Field<T8>, Field<T9>, Field<T10>, Field<T11>, Field<T12>, Field<T13>, Field<T14>, Field<T15>, Field<T16>, Field<T17>, Field<T18>)	- [#7461] - SEEK BEFORE is not implemented correctly
org.jooq.SelectSeekStep18.seekBefore(T1, T2, T3, T4, T5, T6, T7, T8, T9, T10, T11, T12, T13, T14, T15, T16, T17, T18)	- [#7461] - SEEK BEFORE is not implemented correctly
org.jooq.SelectSeekStep19.seekBefore(Field<T1>, Field<T2>, Field<T3>, Field<T4>, Field<T5>, Field<T6>, Field<T7>, Field<T8>, Field<T9>, Field<T10>, Field<T11>, Field<T12>, Field<T13>, Field<T14>, Field<T15>, Field<T16>, Field<T17>, Field<T18>, Field<T19>)	- [#7461] - SEEK BEFORE is not implemented correctly
org.jooq.SelectSeekStep19.seekBefore(T1, T2, T3, T4, T5, T6, T7, T8, T9, T10, T11, T12, T13, T14, T15, T16, T17, T18, T19)	- [#7461] - SEEK BEFORE is not implemented correctly
org.jooq.SelectSeekStep2.seekBefore(Field<T1>, Field<T2>)	- [#7461] - SEEK BEFORE is not implemented correctly
org.jooq.SelectSeekStep2.seekBefore(T1, T2)	- [#7461] - SEEK BEFORE is not implemented correctly
org.jooq.SelectSeekStep20.seekBefore(Field<T1>, Field<T2>, Field<T3>, Field<T4>, Field<T5>, Field<T6>, Field<T7>, Field<T8>, Field<T9>, Field<T10>, Field<T11>, Field<T12>, Field<T13>, Field<T14>, Field<T15>, Field<T16>, Field<T17>, Field<T18>, Field<T19>, Field<T20>)	- [#7461] - SEEK BEFORE is not implemented correctly
org.jooq.SelectSeekStep20.seekBefore(T1, T2, T3, T4, T5, T6, T7, T8, T9, T10, T11, T12, T13, T14, T15, T16, T17, T18, T19, T20)	- [#7461] - SEEK BEFORE is not implemented correctly
org.jooq.SelectSeekStep21.seekBefore(Field<T1>, Field<T2>, Field<T3>, Field<T4>, Field<T5>, Field<T6>, Field<T7>, Field<T8>, Field<T9>, Field<T10>, Field<T11>, Field<T12>, Field<T13>, Field<T14>, Field<T15>, Field<T16>, Field<T17>, Field<T18>, Field<T19>, Field<T20>, Field<T21>)	- [#7461] - SEEK BEFORE is not implemented correctly
org.jooq.SelectSeekStep21.seekBefore(T1, T2, T3, T4, T5, T6, T7, T8, T9, T10, T11, T12, T13, T14, T15, T16, T17, T18, T19, T20, T21)	- [#7461] - SEEK BEFORE is not implemented correctly
org.jooq.SelectSeekStep22.seekBefore(Field<T1>, Field<T2>, Field<T3>, Field<T4>, Field<T5>, Field<T6>, Field<T7>, Field<T8>, Field<T9>, Field<T10>, Field<T11>, Field<T12>, Field<T13>, Field<T14>, Field<T15>, Field<T16>, Field<T17>, Field<T18>, Field<T19>, Field<T20>, Field<T21>, Field<T22>)	- [#7461] - SEEK BEFORE is not implemented correctly
org.jooq.SelectSeekStep22.seekBefore(T1, T2, T3, T4, T5, T6, T7, T8, T9, T10, T11, T12, T13, T14, T15, T16, T17, T18, T19, T20, T21, T22)	- [#7461] - SEEK BEFORE is not implemented correctly
org.jooq.SelectSeekStep3.seekBefore(Field<T1>, Field<T2>, Field<T3>)	- [#7461] - SEEK BEFORE is not implemented correctly
org.jooq.SelectSeekStep3.seekBefore(T1, T2, T3)	- [#7461] - SEEK BEFORE is not implemented correctly
org.jooq.SelectSeekStep4.seekBefore(Field<T1>, Field<T2>, Field<T3>, Field<T4>)	- [#7461] - SEEK BEFORE is not implemented correctly
org.jooq.SelectSeekStep4.seekBefore(T1, T2, T3, T4)	- [#7461] - SEEK BEFORE is not implemented correctly
org.jooq.SelectSeekStep5.seekBefore(Field<T1>, Field<T2>, Field<T3>, Field<T4>, Field<T5>)	- [#7461] - SEEK BEFORE is not implemented correctly
org.jooq.SelectSeekStep5.seekBefore(T1, T2, T3, T4, T5)	- [#7461] - SEEK BEFORE is not implemented correctly
org.jooq.SelectSeekStep6.seekBefore(Field<T1>, Field<T2>, Field<T3>, Field<T4>, Field<T5>, Field<T6>)	- [#7461] - SEEK BEFORE is not implemented correctly
org.jooq.SelectSeekStep6.seekBefore(T1, T2, T3, T4, T5, T6)	- [#7461] - SEEK BEFORE is not implemented correctly
org.jooq.SelectSeekStep7.seekBefore(Field<T1>, Field<T2>, Field<T3>, Field<T4>, Field<T5>, Field<T6>, Field<T7>)	- [#7461] - SEEK BEFORE is not implemented correctly
org.jooq.SelectSeekStep7.seekBefore(T1, T2, T3, T4, T5, T6, T7)	- [#7461] - SEEK BEFORE is not implemented correctly
org.jooq.SelectSeekStep8.seekBefore(Field<T1>, Field<T2>, Field<T3>, Field<T4>, Field<T5>, Field<T6>, Field<T7>, Field<T8>)	- [#7461] - SEEK BEFORE is not implemented correctly
org.jooq.SelectSeekStep8.seekBefore(T1, T2, T3, T4, T5, T6, T7, T8)	- [#7461] - SEEK BEFORE is not implemented correctly
org.jooq.SelectSeekStep9.seekBefore(Field<T1>, Field<T2>, Field<T3>, Field<T4>, Field<T5>, Field<T6>, Field<T7>, Field<T8>, Field<T9>)	- [#7461] - SEEK BEFORE is not implemented correctly
org.jooq.SelectSeekStep9.seekBefore(T1, T2, T3, T4, T5, T6, T7, T8, T9)	- [#7461] - SEEK BEFORE is not implemented correctly
org.jooq.SelectSeekStepN.seekBefore(Object...)	- [#7461] - SEEK BEFORE is not implemented correctly
org.jooq.SelectSeekStepN.seekBefore(Field<?>...)	- [#7461] - SEEK BEFORE is not implemented correctly
org.jooq.SQLDialect.supports(Collection<SQLDialect>)	- [#9882] - 3.14.0 - Use SQLDialect.supportedBy(SQLDialect...) instead
org.jooq.Table.as(String, BiFunction<? super Field<?>, ? super Integer, ? extends String>)	- 3.14.0 - [#10156] - These methods will be removed without replacement from a future jOOQ. They offer convenience that is unidiomatic for jOOQ's DSL, without offering functionality that would not be possible otherwise - yet they add complexity in jOOQ's internals.
org.jooq.Table.as(String, Function<? super Field<?>, ? extends String>)	- 3.14.0 - [#10156] - These methods will be removed without replacement from a future jOOQ. They offer convenience that is unidiomatic for jOOQ's DSL, without offering functionality that would not be possible otherwise - yet they add complexity in jOOQ's internals.
org.jooq.Table.as(Name, BiFunction<? super Field<?>, ? super Integer, ? extends Name>)	- 3.14.0 - [#10156] - These methods will be removed without replacement from a future jOOQ. They offer convenience that is unidiomatic for jOOQ's DSL, without offering functionality that would not be possible otherwise - yet they add complexity in jOOQ's internals.
org.jooq.Table.as(Name, Function<? super Field<?>, ? extends Name>)	- 3.14.0 - [#10156] - These methods will be removed without replacement from a future jOOQ. They offer convenience that is unidiomatic for jOOQ's DSL, without offering functionality that would not be possible otherwise - yet they add complexity in jOOQ's internals.
org.jooq.Table.as(Table<?>, BiFunction<? super Field<?>, ? super Integer, ? extends Field<?>>)	- 3.14.0 - [#10156] - These methods will be removed without replacement from a future jOOQ. They offer convenience that is unidiomatic for jOOQ's DSL, without offering functionality that would not be possible otherwise - yet they add complexity in jOOQ's internals.
org.jooq.Table.as(Table<?>, Function<? super Field<?>, ? extends Field<?>>)	- 3.14.0 - [#10156] - These methods will be removed without replacement from a future jOOQ. They offer convenience that is unidiomatic for jOOQ's DSL, without offering functionality that would not be possible otherwise - yet they add complexity in jOOQ's internals.
org.jooq.TableLike.asTable(String, BiFunction<? super Field<?>, ? super Integer, ? extends String>)	- 3.14.0 - [#10156] - These methods will be removed without replacement from a future jOOQ. They offer convenience that is unidiomatic for jOOQ's DSL, without offering functionality that would not be possible otherwise - yet they add complexity in jOOQ's internals.
org.jooq.TableLike.asTable(String, Function<? super Field<?>, ? extends String>)	- 3.14.0 - [#10156] - These methods will be removed without replacement from a future jOOQ. They offer convenience that is unidiomatic for jOOQ's DSL, without offering functionality that would not be possible otherwise - yet they add complexity in jOOQ's internals.
org.jooq.tools.jdbc.DefaultCallableStatement.getBigDecimal(int, int)
org.jooq.tools.jdbc.DefaultPreparedStatement.setUnicodeStream(int, InputStream, int)
org.jooq.tools.jdbc.DefaultResultSet.getBigDecimal(int, int)
org.jooq.tools.jdbc.DefaultResultSet.getBigDecimal(String, int)
org.jooq.tools.jdbc.DefaultResultSet.getUnicodeStream(int)
org.jooq.tools.jdbc.DefaultResultSet.getUnicodeStream(String)
org.jooq.tools.jdbc.MockFileDatabase.nullLiteral(String)	- Use MockFileDatabaseConfiguration.nullLiteral(String) instead.
org.jooq.tools.jdbc.MockFileDatabase.queries()	- Experimental: Do not use. Subject to change.
org.jooq.tools.jdbc.MockResultSet.getBigDecimal(int, int)
org.jooq.tools.jdbc.MockResultSet.getBigDecimal(String, int)
org.jooq.tools.jdbc.MockResultSet.getUnicodeStream(int)
org.jooq.tools.jdbc.MockResultSet.getUnicodeStream(String)
org.jooq.tools.reflect.Reflect.on(Class<?>)	[#78] 0.9.11, use Reflect.onClass(Class) instead.
org.jooq.tools.reflect.Reflect.on(String)	[#78] 0.9.11, use Reflect.onClass(String) instead.
org.jooq.tools.reflect.Reflect.on(String, ClassLoader)	[#78] 0.9.11, use Reflect.onClass(String, ClassLoader) instead.
org.jooq.util.mysql.MySQLDSL.decode(byte[], byte[])	- 3.15.0 - [#8611] - This function has been removed from MySQL 8
org.jooq.util.mysql.MySQLDSL.decode(String, String)	- 3.15.0 - [#8611] - This function has been removed from MySQL 8
org.jooq.util.mysql.MySQLDSL.decode(Field<T>, Field<T>)	- 3.15.0 - [#8611] - This function has been removed from MySQL 8
org.jooq.util.mysql.MySQLDSL.desDecrypt(byte[])	- 3.15.0 - [#8611] - This function has been removed from MySQL 8
org.jooq.util.mysql.MySQLDSL.desDecrypt(byte[], byte[])	- 3.15.0 - [#8611] - This function has been removed from MySQL 8
org.jooq.util.mysql.MySQLDSL.desDecrypt(String)	- 3.15.0 - [#8611] - This function has been removed from MySQL 8
org.jooq.util.mysql.MySQLDSL.desDecrypt(String, String)	- 3.15.0 - [#8611] - This function has been removed from MySQL 8
org.jooq.util.mysql.MySQLDSL.desDecrypt(Field<T>)	- 3.15.0 - [#8611] - This function has been removed from MySQL 8
org.jooq.util.mysql.MySQLDSL.desDecrypt(Field<T>, Field<T>)	- 3.15.0 - [#8611] - This function has been removed from MySQL 8
org.jooq.util.mysql.MySQLDSL.desEncrypt(byte[])	- 3.15.0 - [#8611] - This function has been removed from MySQL 8
org.jooq.util.mysql.MySQLDSL.desEncrypt(byte[], byte[])	- 3.15.0 - [#8611] - This function has been removed from MySQL 8
org.jooq.util.mysql.MySQLDSL.desEncrypt(String)	- 3.15.0 - [#8611] - This function has been removed from MySQL 8
org.jooq.util.mysql.MySQLDSL.desEncrypt(String, String)	- 3.15.0 - [#8611] - This function has been removed from MySQL 8
org.jooq.util.mysql.MySQLDSL.desEncrypt(Field<T>)	- 3.15.0 - [#8611] - This function has been removed from MySQL 8
org.jooq.util.mysql.MySQLDSL.desEncrypt(Field<T>, Field<T>)	- 3.15.0 - [#8611] - This function has been removed from MySQL 8
org.jooq.util.mysql.MySQLDSL.encode(byte[], byte[])	- 3.15.0 - [#8611] - This function has been removed from MySQL 8
org.jooq.util.mysql.MySQLDSL.encode(String, String)	- 3.15.0 - [#8611] - This function has been removed from MySQL 8
org.jooq.util.mysql.MySQLDSL.encode(Field<T>, Field<T>)	- 3.15.0 - [#8611] - This function has been removed from MySQL 8
org.jooq.util.mysql.MySQLDSL.password(byte[])	- 3.15.0 - [#8611] - This function has been removed from MySQL 8
org.jooq.util.mysql.MySQLDSL.password(String)	- 3.15.0 - [#8611] - This function has been removed from MySQL 8
org.jooq.util.mysql.MySQLDSL.password(Field<T>)	- 3.15.0 - [#8611] - This function has been removed from MySQL 8
org.jooq.util.mysql.MySQLDSL.values(Field<T>)	- 3.15.0 - [#12099] - MySQL 8.0.20 has deprecated this clause and replaced it by something new, which we'll support soon, see https://dev.mysql.com/doc/refman/8.0/en/insert-on-duplicate.html/ and https://github.com/jOOQ/jOOQ/issues/12099
org.jooq.util.oracle.OracleDSL.DBMS_AQ.MESSAGE_PROPERTIES_T.expires(BigDecimal)	- use OracleDSL.DBMS_AQ.MESSAGE_PROPERTIES_T.expiration(BigDecimal) instead.
org.jooq.util.oracle.OracleDSL.toChar(Object)	- 3.14.0 - [#8381] [#10641] - Use DSL.toChar(Field, Field) instead.
org.jooq.util.oracle.OracleDSL.toChar(Object, String)	- 3.14.0 - [#8381] [#10641] - Use DSL.toChar(Field, Field) instead.
org.jooq.util.oracle.OracleDSL.toChar(Object, Field<String>)	- 3.14.0 - [#8381] [#10641] - Use DSL.toChar(Field, Field) instead.
org.jooq.util.oracle.OracleDSL.toChar(Field<?>)	- 3.14.0 - [#8381] [#10641] - Use DSL.toChar(Field, Field) instead.
org.jooq.util.oracle.OracleDSL.toChar(Field<?>, String)	- 3.14.0 - [#8381] [#10641] - Use DSL.toChar(Field, Field) instead.
org.jooq.util.oracle.OracleDSL.toChar(Field<?>, Field<String>)	- 3.14.0 - [#8381] [#10641] - Use DSL.toChar(Field, Field) instead.
org.jooq.util.postgres.PostgresDSL.oid(Table<?>)	- [#12420] - 3.16.0 - Use actual OID column references in jOOQ-meta, instead.
org.jooq.WindowPartitionByStep.partitionByOne()	- 3.10 - [#6427] - This synthetic clause is no longer supported, use WindowPartitionByStep.partitionBy(Field...) instead, or omit the clause entirely.
org.jooq.WindowSpecificationPartitionByStep.partitionByOne()	- 3.10 - [#6427] - This synthetic clause is no longer supported, use WindowSpecificationPartitionByStep.partitionBy(Field...) instead, or omit the clause entirely.
org.jooq.WithStep.mergeInto(Table<R>, Field<T1>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via WithStep.mergeInto(Table)
org.jooq.WithStep.mergeInto(Table<R>, Field<T1>, Field<T2>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via WithStep.mergeInto(Table)
org.jooq.WithStep.mergeInto(Table<R>, Field<T1>, Field<T2>, Field<T3>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via WithStep.mergeInto(Table)
org.jooq.WithStep.mergeInto(Table<R>, Field<T1>, Field<T2>, Field<T3>, Field<T4>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via WithStep.mergeInto(Table)
org.jooq.WithStep.mergeInto(Table<R>, Field<T1>, Field<T2>, Field<T3>, Field<T4>, Field<T5>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via WithStep.mergeInto(Table)
org.jooq.WithStep.mergeInto(Table<R>, Field<T1>, Field<T2>, Field<T3>, Field<T4>, Field<T5>, Field<T6>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via WithStep.mergeInto(Table)
org.jooq.WithStep.mergeInto(Table<R>, Field<T1>, Field<T2>, Field<T3>, Field<T4>, Field<T5>, Field<T6>, Field<T7>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via WithStep.mergeInto(Table)
org.jooq.WithStep.mergeInto(Table<R>, Field<T1>, Field<T2>, Field<T3>, Field<T4>, Field<T5>, Field<T6>, Field<T7>, Field<T8>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via WithStep.mergeInto(Table)
org.jooq.WithStep.mergeInto(Table<R>, Field<T1>, Field<T2>, Field<T3>, Field<T4>, Field<T5>, Field<T6>, Field<T7>, Field<T8>, Field<T9>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via WithStep.mergeInto(Table)
org.jooq.WithStep.mergeInto(Table<R>, Field<T1>, Field<T2>, Field<T3>, Field<T4>, Field<T5>, Field<T6>, Field<T7>, Field<T8>, Field<T9>, Field<T10>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via WithStep.mergeInto(Table)
org.jooq.WithStep.mergeInto(Table<R>, Field<T1>, Field<T2>, Field<T3>, Field<T4>, Field<T5>, Field<T6>, Field<T7>, Field<T8>, Field<T9>, Field<T10>, Field<T11>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via WithStep.mergeInto(Table)
org.jooq.WithStep.mergeInto(Table<R>, Field<T1>, Field<T2>, Field<T3>, Field<T4>, Field<T5>, Field<T6>, Field<T7>, Field<T8>, Field<T9>, Field<T10>, Field<T11>, Field<T12>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via WithStep.mergeInto(Table)
org.jooq.WithStep.mergeInto(Table<R>, Field<T1>, Field<T2>, Field<T3>, Field<T4>, Field<T5>, Field<T6>, Field<T7>, Field<T8>, Field<T9>, Field<T10>, Field<T11>, Field<T12>, Field<T13>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via WithStep.mergeInto(Table)
org.jooq.WithStep.mergeInto(Table<R>, Field<T1>, Field<T2>, Field<T3>, Field<T4>, Field<T5>, Field<T6>, Field<T7>, Field<T8>, Field<T9>, Field<T10>, Field<T11>, Field<T12>, Field<T13>, Field<T14>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via WithStep.mergeInto(Table)
org.jooq.WithStep.mergeInto(Table<R>, Field<T1>, Field<T2>, Field<T3>, Field<T4>, Field<T5>, Field<T6>, Field<T7>, Field<T8>, Field<T9>, Field<T10>, Field<T11>, Field<T12>, Field<T13>, Field<T14>, Field<T15>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via WithStep.mergeInto(Table)
org.jooq.WithStep.mergeInto(Table<R>, Field<T1>, Field<T2>, Field<T3>, Field<T4>, Field<T5>, Field<T6>, Field<T7>, Field<T8>, Field<T9>, Field<T10>, Field<T11>, Field<T12>, Field<T13>, Field<T14>, Field<T15>, Field<T16>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via WithStep.mergeInto(Table)
org.jooq.WithStep.mergeInto(Table<R>, Field<T1>, Field<T2>, Field<T3>, Field<T4>, Field<T5>, Field<T6>, Field<T7>, Field<T8>, Field<T9>, Field<T10>, Field<T11>, Field<T12>, Field<T13>, Field<T14>, Field<T15>, Field<T16>, Field<T17>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via WithStep.mergeInto(Table)
org.jooq.WithStep.mergeInto(Table<R>, Field<T1>, Field<T2>, Field<T3>, Field<T4>, Field<T5>, Field<T6>, Field<T7>, Field<T8>, Field<T9>, Field<T10>, Field<T11>, Field<T12>, Field<T13>, Field<T14>, Field<T15>, Field<T16>, Field<T17>, Field<T18>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via WithStep.mergeInto(Table)
org.jooq.WithStep.mergeInto(Table<R>, Field<T1>, Field<T2>, Field<T3>, Field<T4>, Field<T5>, Field<T6>, Field<T7>, Field<T8>, Field<T9>, Field<T10>, Field<T11>, Field<T12>, Field<T13>, Field<T14>, Field<T15>, Field<T16>, Field<T17>, Field<T18>, Field<T19>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via WithStep.mergeInto(Table)
org.jooq.WithStep.mergeInto(Table<R>, Field<T1>, Field<T2>, Field<T3>, Field<T4>, Field<T5>, Field<T6>, Field<T7>, Field<T8>, Field<T9>, Field<T10>, Field<T11>, Field<T12>, Field<T13>, Field<T14>, Field<T15>, Field<T16>, Field<T17>, Field<T18>, Field<T19>, Field<T20>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via WithStep.mergeInto(Table)
org.jooq.WithStep.mergeInto(Table<R>, Field<T1>, Field<T2>, Field<T3>, Field<T4>, Field<T5>, Field<T6>, Field<T7>, Field<T8>, Field<T9>, Field<T10>, Field<T11>, Field<T12>, Field<T13>, Field<T14>, Field<T15>, Field<T16>, Field<T17>, Field<T18>, Field<T19>, Field<T20>, Field<T21>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via WithStep.mergeInto(Table)
org.jooq.WithStep.mergeInto(Table<R>, Field<T1>, Field<T2>, Field<T3>, Field<T4>, Field<T5>, Field<T6>, Field<T7>, Field<T8>, Field<T9>, Field<T10>, Field<T11>, Field<T12>, Field<T13>, Field<T14>, Field<T15>, Field<T16>, Field<T17>, Field<T18>, Field<T19>, Field<T20>, Field<T21>, Field<T22>)	- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, via WithStep.mergeInto(Table)
org.jooq.WithStep.with(String, BiFunction<? super Field<?>, ? super Integer, ? extends String>)	- 3.14.0 - [#10156] - These methods will be removed without replacement from a future jOOQ. They offer convenience that is unidiomatic for jOOQ's DSL, without offering functionality that would not be possible otherwise - yet they add complexity in jOOQ's internals.
org.jooq.WithStep.with(String, Function<? super Field<?>, ? extends String>)	- 3.14.0 - [#10156] - These methods will be removed without replacement from a future jOOQ. They offer convenience that is unidiomatic for jOOQ's DSL, without offering functionality that would not be possible otherwise - yet they add complexity in jOOQ's internals.

Deprecated Constructors

Constructor	Description
org.jooq.impl.CustomTable(String)	- 3.10 - [#5996] - Use CustomTable(Name) instead.
org.jooq.impl.CustomTable(String, Schema)	- 3.10 - [#5996] - Use CustomTable(Name, Schema) instead.
org.jooq.impl.DefaultBinding(Converter<T, U>)	- 3.11 - [#6631] - Use DefaultBinding.binding(Converter) instead.
org.jooq.impl.EmbeddableRecordImpl(Field<?>...)	- [#11058] - 3.14.5 - Please re-generate your code.
org.jooq.impl.EmbeddableRecordImpl(TableField<?, ?>...)	- [#11058] - 3.14.5 - Please re-generate your code.
org.jooq.impl.SequenceImpl(String, Schema, DataType<T>)
org.jooq.impl.TableImpl(String)	- 3.10 - [#5996] - Use TableImpl(Name) instead (or re-generated your code).
org.jooq.impl.TableImpl(String, Schema)	- 3.10 - [#5996] - Use TableImpl(Name, Schema) instead (or re-generated your code).
org.jooq.impl.TableImpl(String, Schema, Table<R>)	- 3.10 - [#5996] - Use TableImpl(Name, Schema, Table) instead (or re-generated your code).
org.jooq.impl.TableImpl(String, Schema, Table<R>, Field<?>[])	- 3.10 - [#5996] - Use TableImpl(Name, Schema, Table, Field[]) instead (or re-generated your code).
org.jooq.impl.TableImpl(String, Schema, Table<R>, Field<?>[], String)	- 3.10 - [#5996] - Use TableImpl(Name, Schema, Table, Field[], String) instead (or re-generated your code).
org.jooq.impl.TableImpl(Name, Schema, Table<R>, Field<?>[], String)	- 3.11 - [#7027] - Use TableImpl(Name, Schema, Table, Field[], Comment) instead.

Deprecated Enum Constants

Enum Constant	Description
org.jooq.SQLDialect.CUBRID	- [#9403] - 3.13.0 - This dialect is hardly used by anyone with jOOQ or without jOOQ and will be removed in the near future.
org.jooq.SQLDialect.IGNITE	- [#12465] - 3.16.0 - This dialect is hardly used by anyone with jOOQ or without jOOQ and will be removed in the near future. If you're actively using this dialect, please get in touch for extended support: https://github.com/jOOQ/jOOQ/issues/12465
org.jooq.SQLDialect.INGRES	- [#11515] - 3.15.0 - This dialect is hardly used by anyone with jOOQ or without jOOQ and will be removed in the near future. If you're actively using this dialect, please get in touch for extended support: https://github.com/jOOQ/jOOQ/issues/11515
org.jooq.SQLDialect.ORACLE10G	- [#11797] - 3.15.0 - This dialect is no longer supported. If you continue to require support for Oracle 10g, please get in touch here: https://github.com/jOOQ/jOOQ/issues/11797
org.jooq.SQLDialect.POSTGRESPLUS	- This dialect is not yet supported by jOOQ.