Deprecated API
Contents
- Terminally Deprecated
- Packages
- Interfaces
- Classes
- Enum Classes
- Exception Classes
- Annotation Interfaces
- Fields
- Methods
- Constructors
- Enum Constants
-
Terminally Deprecated ElementsElementDescription- [#11329] - 3.15.0 - This type will be removed in the future. Do not reference it directly- [#11329] - 3.15.0 - This type will be removed in the future. Do not reference it directly- [#11329] - 3.15.0 - This type will be removed in the future. Do not reference it directly- [#11329] - 3.15.0 - This type will be removed in the future. Do not reference it directly- [#11329] - 3.15.0 - This type will be removed in the future. Do not reference it directly- [#11329] - 3.15.0 - This type will be removed in the future. Do not reference it directly- [#11329] - 3.15.0 - This type will be removed in the future. Do not reference it directly- [#11329] - 3.15.0 - This type will be removed in the future. Do not reference it directly- 3.11.0 - [#7258] - This part of the
VisitListenerSPI 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- [#11329] - 3.15.0 - This type will be removed in the future. Do not reference it directly- 3.14.0 - [#9911] - This method is no longer supported.- 3.14.0 - [#9911] - This method is no longer supported.- 3.14.0 - [#9911] - This method is no longer supported.- 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.- 2.0.5 - UseConfiguration.settings()instead- [#11329] - 3.15.0 - This type will be removed in the future. Do not reference it directly- [#10317] - 3.14.0 - Do not reuse this method. It will be removed without replacement.- [#10317] - 3.14.0 - Do not reuse this method. It will be removed without replacement.- [#10689] - 3.14.0 - This converter does not work. Do not use this method, useConverters.identity(Class)instead.- [#10689] - 3.14.0 - This method does not provide any useful functionality and will be removed in the future.- [#11329] - 3.15.0 - This type will be removed in the future. Do not reference it directly- [#11329] - 3.15.0 - This type will be removed in the future. Do not reference it directly- [#11329] - 3.15.0 - This type will be removed in the future. Do not reference it directly- [#11329] - 3.15.0 - This type will be removed in the future. Do not reference it directly- [#11329] - 3.15.0 - This type will be removed in the future. Do not reference it directly- [#11329] - 3.15.0 - This type will be removed in the future. Do not reference it directly- [#11329] - 3.15.0 - This type will be removed in the future. Do not reference it directly- [#11329] - 3.15.0 - This type will be removed in the future. Do not reference it directly- 3.15.0 - [#11902] - UseIterable.forEach(Consumer)based methods, instead.- 3.15.0 - [#11902] - UseIterable.forEach(Consumer)based methods, instead.- 3.20.0 - [#16810] - Static data type conversion has been a controversial historic feature of jOOQ. While occasionally useful for internal data types (such asStringtoIntegerconversion, etc.) it doesn't work well with user defined types. 1) This method does not go throughConfiguration.converterProvider(), 2) nor does it provide an appropriateConverterContextto aContextConverter, leading to subtle bugs. 3) It also doesn't make any guarantees related to what user defined types can be passed to it. This is why this method is deprecated and will be removed in a future jOOQ version. UseDataType.getConverter()on this type, instead, and use that for data type conversions.- 3.20.0 - [#16810] - Static data type conversion has been a controversial historic feature of jOOQ. While occasionally useful for internal data types (such asStringtoIntegerconversion, etc.) it doesn't work well with user defined types. 1) This method does not go throughConfiguration.converterProvider(), 2) nor does it provide an appropriateConverterContextto aContextConverter, leading to subtle bugs. 3) It also doesn't make any guarantees related to what user defined types can be passed to it. This is why this method is deprecated and will be removed in a future jOOQ version. UseDataType.getConverter()on this type, instead, and use that for data type conversions.- 3.20.0 - [#16810] - Static data type conversion has been a controversial historic feature of jOOQ. While occasionally useful for internal data types (such asStringtoIntegerconversion, etc.) it doesn't work well with user defined types. 1) This method does not go throughConfiguration.converterProvider(), 2) nor does it provide an appropriateConverterContextto aContextConverter, leading to subtle bugs. 3) It also doesn't make any guarantees related to what user defined types can be passed to it. This is why this method is deprecated and will be removed in a future jOOQ version. UseDataType.getConverter()on this type, instead, and use that for data type conversions.- 3.21.0 - [#18732] - UseDataType.isQualifiedRecord()instead, orDataType.isUDTRecord()if that's more precise.- [#11329] - 3.15.0 - This type will be removed in the future. Do not reference it directly- [#11329] - 3.15.0 - This type will be removed in the future. Do not reference it directly- [#11329] - 3.15.0 - This type will be removed in the future. Do not reference it directly- [#11329] - 3.15.0 - This type will be removed in the future. Do not reference it directly- [#11329] - 3.15.0 - This type will be removed in the future. Do not reference it directly- [#11329] - 3.15.0 - This type will be removed in the future. Do not reference it directly- [#11329] - 3.15.0 - This type will be removed in the future. Do not reference it directly- [#11329] - 3.15.0 - This type will be removed in the future. Do not reference it directly- [#11329] - 3.15.0 - This type will be removed in the future. Do not reference it directly- [#6280] - 3.10 - Do not reuse this method. It will be completely internal with jOOQ 4.0- 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.- 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.- 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.- 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.- 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.- 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.- 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.- 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.- 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.- 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.- 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.- 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.- 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.- 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.- 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.- 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.- 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.- 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.- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#6280] - 3.10 - Do not reuse this method. It will be completely internal with jOOQ 4.0- 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.- 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.- 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.- 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.- 3.11 - [#7538] - UseDSL.abs(Field)instead.- 3.11 - [#7538] - UseDSL.acos(Field)instead.- 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.- 3.13 - [#9407] - UseDSL.ascii(Field)instead.- 3.11 - [#7538] - UseDSL.asin(Field)instead.- 3.11 - [#7538] - UseDSL.atan(Field)instead.- 3.11 - [#7538] - UseDSL.atan2(Field, Number)instead.- 3.11 - [#7538] - UseDSL.atan2(Field, Field)instead.- 3.11 - [#7538] - UseDSL.avg(Field)instead.- 3.11 - [#7538] - UseDSL.avg(Field)instead.- 3.13 - [#9407] - UseDSL.bitLength(Field)instead.- 3.11 - [#7538] - UseDSL.ceil(Field)instead.- [#12494] - 3.20.0 - UseField.touched(Record)instead.- 3.13 - [#9407] - UseDSL.charLength(Field)instead.- 3.13 - [#9407] - UseDSL.coalesce(Field, Field...)instead.- 3.13 - [#9407] - UseDSL.coalesce(Object, Object...)instead.- 3.11 - [#7538] - UseDSL.cos(Field)instead.- 3.11 - [#7538] - UseDSL.cosh(Field)instead.- 3.11 - [#7538] - UseDSL.cot(Field)instead.- 3.11 - [#7538] - UseDSL.coth(Field)instead.- 3.11 - [#7538] - UseDSL.count(Field)instead.- 3.11 - [#7538] - UseDSL.countDistinct(Field)instead.- 3.11 - [#7538] - UseDSL.count(Field)instead.- 3.13 - [#9407] - UseDSL.decode(Field, Field, Field)instead.- 3.13 - [#9407] - UseDSL.decode(Field, Field, Field, Field...)instead.- 3.13 - [#9407] - UseDSL.decode(Object, Object, Object)instead.- 3.13 - [#9407] - UseDSL.decode(Object, Object, Object, Object...)instead.- 3.11 - [#7538] - UseDSL.deg(Field)instead.- 3.11 - [#7538] - UseDSL.exp(Field)instead.- 3.11 - [#7538] - UseDSL.extract(Field, DatePart)instead.- 3.11 - [#7538] - UseDSL.firstValue(Field)instead.- 3.11 - [#7538] - UseDSL.floor(Field)instead.- 3.11 - [#7538] - UseDSL.greatest(Field, Field...)instead.- 3.11 - [#7538] - UseDSL.greatest(Field, Field...)instead.- 3.11 - [#7538] - UseDSL.lag(Field)instead.- 3.11 - [#7538] - UseDSL.lag(Field, int)instead.- 3.11 - [#7538] - UseDSL.lag(Field, int, Field)instead.- 3.11 - [#7538] - UseDSL.lag(Field, int, Object)instead.- 3.11 - [#7538] - UseDSL.lastValue(Field)instead.- 3.11 - [#7538] - UseDSL.lead(Field)instead.- 3.11 - [#7538] - UseDSL.lead(Field, int)instead.- 3.11 - [#7538] - UseDSL.lead(Field, int, Field)instead.- 3.11 - [#7538] - UseDSL.lead(Field, int, Object)instead.- 3.11 - [#7538] - UseDSL.least(Field, Field...)instead.- 3.11 - [#7538] - UseDSL.least(Field, Field...)instead.- 3.13 - [#9407] - UseDSL.length(Field)instead.- 3.11 - [#7538] - UseDSL.ln(Field)instead.- 3.11 - [#7538] - UseDSL.log(Field, int)instead.- 3.13 - [#9407] - UseDSL.lower(Field)instead.- 3.13 - [#9407] - UseDSL.lpad(Field, int)instead.- 3.13 - [#9407] - UseDSL.lpad(Field, int, char)instead.- 3.13 - [#9407] - UseDSL.lpad(Field, Field)instead.- 3.13 - [#9407] - UseDSL.lpad(Field, Field, Field)instead.- 3.13 - [#9407] - UseDSL.ltrim(Field)instead.- 3.11 - [#7538] - UseDSL.max(Field)instead.- 3.11 - [#7538] - UseDSL.max(Field)instead.- 3.11 - [#7538] - UseDSL.median(Field)instead.- 3.11 - [#7538] - UseDSL.min(Field)instead.- 3.11 - [#7538] - UseDSL.min(Field)instead.- 3.13 - [#9407] - UseDSL.nullif(Field, Field)instead.- 3.13 - [#9407] - UseDSL.nullif(Field, Object)instead.- 3.13 - [#9407] - UseDSL.nvl(Field, Field)instead.- 3.13 - [#9407] - UseDSL.nvl(Field, Object)instead.- 3.13 - [#9407] - UseDSL.nvl2(Field, Field, Field)instead.- 3.13 - [#9407] - UseDSL.nvl2(Field, Object, Object)instead.- 3.13 - [#9407] - UseDSL.octetLength(Field)instead.- 3.13 - [#9407] - UseDSL.position(Field, String)instead.- 3.13 - [#9407] - UseDSL.position(Field, Field)instead.- 3.11 - [#7538] - UseDSL.rad(Field)instead.- 3.13 - [#9407] - UseDSL.repeat(Field, int)instead.- 3.13 - [#9407] - UseDSL.repeat(Field, Field)instead.- 3.13 - [#9407] - UseDSL.replace(Field, String)instead.- 3.13 - [#9407] - UseDSL.replace(Field, String, String)instead.- 3.13 - [#9407] - UseDSL.replace(Field, Field)instead.- 3.13 - [#9407] - UseDSL.replace(Field, Field, Field)instead.- 3.11 - [#7538] - UseDSL.round(Field)instead.- 3.11 - [#7538] - UseDSL.round(Field, int)instead.- 3.13 - [#9407] - UseDSL.rpad(Field, int)instead.- 3.13 - [#9407] - UseDSL.rpad(Field, int, char)instead.- 3.13 - [#9407] - UseDSL.rpad(Field, Field)instead.- 3.13 - [#9407] - UseDSL.rpad(Field, Field, Field)instead.- 3.13 - [#9407] - UseDSL.rtrim(Field)instead.- 3.11 - [#7538] - UseDSL.sign(Field)instead.- 3.11 - [#7538] - UseDSL.sin(Field)instead.- 3.11 - [#7538] - UseDSL.sinh(Field)instead.- 3.11 - [#7538] - UseDSL.sqrt(Field)instead.- 3.11 - [#7538] - UseDSL.stddevPop(Field)instead.- 3.11 - [#7538] - UseDSL.stddevPop(Field)instead.- 3.11 - [#7538] - UseDSL.stddevSamp(Field)instead.- 3.11 - [#7538] - UseDSL.stddevSamp(Field)instead.- 3.13 - [#9407] - UseDSL.substring(Field, int)instead.- 3.13 - [#9407] - UseDSL.substring(Field, int, int)instead.- 3.13 - [#9407] - UseDSL.substring(Field, Field)instead.- 3.13 - [#9407] - UseDSL.substring(Field, Field, Field)instead.- 3.11 - [#7538] - UseDSL.sum(Field)instead.- 3.11 - [#7538] - UseDSL.sum(Field)instead.- 3.11 - [#7538] - UseDSL.tan(Field)instead.- 3.11 - [#7538] - UseDSL.tanh(Field)instead.- 3.13 - [#9407] - UseDSL.trim(Field)instead.- 3.13 - [#9407] - UseDSL.upper(Field)instead.- 3.11 - [#7538] - UseDSL.varPop(Field)instead.- 3.11 - [#7538] - UseDSL.varPop(Field)instead.- 3.11 - [#7538] - UseDSL.varSamp(Field)instead.- 3.11 - [#7538] - UseDSL.varSamp(Field)instead.- 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.- 3.21.0 - [#19250] - This method will be removed in the future. Please use one of the alternative XML formatting methods, instead.- 3.21.0 - [#19250] - This method will be removed in the future. Please use one of the alternative XML formatting methods, instead.- [#11329] - 3.15.0 - This type will be removed in the future. Do not reference it directly- 3.21.0 - [#19125] - This class will be removed from public API, do not reuse.- 3.11 - [#6631] - UseDefaultBinding.binding(Converter)instead.- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDefaultDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDefaultDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDefaultDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDefaultDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDefaultDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDefaultDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDefaultDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDefaultDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDefaultDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDefaultDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDefaultDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDefaultDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDefaultDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDefaultDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDefaultDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDefaultDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDefaultDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDefaultDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDefaultDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDefaultDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDefaultDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDefaultDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDefaultDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDefaultDSLContext.mergeInto(Table)- 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.- 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.- 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.- 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.- 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.- 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.- 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.- 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.- 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.- 3.11.0 - [#7483] - The (indirect) use of the internal static data type registry is not recommended.- [#7956] - 3.12.0 - UseDSL.groupConcat(Field)andGroupConcatSeparatorStep.separator(String)instead.- [#15196] - 3.19.0 - The semantics of theFieldarguments in this method is inconsistent with that of other overloads, such asDSL.jsonbObject(Field, Field), which can lead to subtle bugs. Please refrain from using this overload as it will be removed in the future. UseDSL.jsonObject(JSONEntry...)instead.- [#15196] - 3.19.0 - The semantics of theFieldarguments in this method is inconsistent with that of other overloads, such asDSL.jsonbObject(Field, Field), which can lead to subtle bugs. Please refrain from using this overload as it will be removed in the future. UseDSL.jsonObject(JSONEntry...)instead.- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSL.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSL.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSL.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSL.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSL.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSL.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSL.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSL.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSL.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSL.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSL.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSL.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSL.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSL.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSL.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSL.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSL.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSL.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSL.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSL.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSL.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSL.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSL.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSL.mergeInto(Table)- [#11092] - 3.15.0 - This method will be removed without public replacement.- [#11092] - 3.15.0 - This method will be removed without public replacement.- [#11092] - 3.15.0 - This method will be removed without public replacement.- [#11092] - 3.15.0 - This method will be removed without public replacement.- [#11092] - 3.15.0 - This method will be removed without public replacement.- [#11092] - 3.15.0 - This method will be removed without public replacement.- [#11092] - 3.15.0 - This method will be removed without public replacement.- [#11812] - 3.15.0 - UseRow1as aSelectFielddirectly, instead.- [#11812] - 3.15.0 - UseRow10as aSelectFielddirectly, instead.- [#11812] - 3.15.0 - UseRow11as aSelectFielddirectly, instead.- [#11812] - 3.15.0 - UseRow12as aSelectFielddirectly, instead.- [#11812] - 3.15.0 - UseRow13as aSelectFielddirectly, instead.- [#11812] - 3.15.0 - UseRow14as aSelectFielddirectly, instead.- [#11812] - 3.15.0 - UseRow15as aSelectFielddirectly, instead.- [#11812] - 3.15.0 - UseRow16as aSelectFielddirectly, instead.- [#11812] - 3.15.0 - UseRow17as aSelectFielddirectly, instead.- [#11812] - 3.15.0 - UseRow18as aSelectFielddirectly, instead.- [#11812] - 3.15.0 - UseRow19as aSelectFielddirectly, instead.- [#11812] - 3.15.0 - UseRow2as aSelectFielddirectly, instead.- [#11812] - 3.15.0 - UseRow20as aSelectFielddirectly, instead.- [#11812] - 3.15.0 - UseRow21as aSelectFielddirectly, instead.- [#11812] - 3.15.0 - UseRow22as aSelectFielddirectly, instead.- [#11812] - 3.15.0 - UseRow3as aSelectFielddirectly, instead.- [#11812] - 3.15.0 - UseRow4as aSelectFielddirectly, instead.- [#11812] - 3.15.0 - UseRow5as aSelectFielddirectly, instead.- [#11812] - 3.15.0 - UseRow6as aSelectFielddirectly, instead.- [#11812] - 3.15.0 - UseRow7as aSelectFielddirectly, instead.- [#11812] - 3.15.0 - UseRow8as aSelectFielddirectly, instead.- [#11812] - 3.15.0 - UseRow9as aSelectFielddirectly, instead.- [#11812] - 3.15.0 - UseRowNas aSelectFielddirectly, instead.- 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.- 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.- 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.- 3.14.0 - [#9404] - Please re-generate your code.- 3.21.0 - [#19044] - UseInternal.createParameter(String, DataType, boolean)instead.- 3.21.0 - [#19044] - UseInternal.createParameter(String, DataType, boolean, Binding)instead.- 3.21.0 - [#19044] - UseInternal.createParameter(String, DataType, boolean, Converter)instead.- 3.21.0 - [#19044] - UseInternal.createParameter(String, DataType, boolean, Converter, Binding)instead.- 3.14.0 - [#9404] - Please re-generate your code.- 3.14.0 - [#9404] - Please re-generate your code.- [#11058] - 3.14.5 - Please re-generate your code.- [#12238] - 3.16.0 - Please re-generate your code.- 3.21.0 - [#18684] - UseQOM.CommentOn.$objectType()instead.- 3.21.0 - [#18684] - UseQOM.CommentOn.$objectType()instead.- 3.21.0 - [#18684] - UseQOM.CommentOn.$objectType()instead.- 3.21.0 - [#18684] - UseQOM.CommentOn.$objectType()instead.- 3.21.0 - [#18603] - UseQOM.CreateTable.$tableScope()instead.- 3.21.0 - [#18603] - UseQOM.CreateTable.$tableScope()instead.- 3.21.0 - [#18603] - UseQOM.DropTable.$tableScope()instead.- 3.21.0 - [#18603] - UseQOM.DropTable.$tableScope()instead.- 3.21.0 - [#19277] - UseQOM.MultisetAgg.$fields()instead.- [#12425] - 3.16.0 - Missing implementations should be added as soon as possible!- [#11329] - 3.15.0 - This type will be removed in the future. Do not reference it directly- 3.14.0 - [#10010] - UseLoaderCSVStep.fieldsCorresponding()instead.- 3.14.0 - [#10010] - UseLoaderJSONStep.fieldsCorresponding()instead.- 3.14.0 - [#4941] - UseLoaderListenerStep.onRowEnd(LoaderRowListener)instead.- 3.14.0 - [#10010] - UseLoaderRowsStep.fieldsCorresponding()instead.- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#11329] - 3.15.0 - This type will be removed in the future. Do not reference it directly- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- 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.- 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.- 3.12.0 - [#8163] - UsePivotForStep.for_(Field)instead.- [#12494] - 3.20.0 - UseRecord.touched()instead.- [#12494] - 3.20.0 - UseRecord.touched(boolean)instead.- [#12494] - 3.20.0 - UseRecord.touched(int)instead.- [#12494] - 3.20.0 - UseRecord.touched(int, boolean)instead.- [#12494] - 3.20.0 - UseRecord.touched(String)instead.- [#12494] - 3.20.0 - UseRecord.touched(String, boolean)instead.- [#12494] - 3.20.0 - UseRecord.touched(Field)instead.- [#12494] - 3.20.0 - UseRecord.touched(Field, boolean)instead.- [#12494] - 3.20.0 - UseRecord.touched(Name)instead.- [#12494] - 3.20.0 - UseRecord.touched(Name, boolean)instead.- 3.15.0 - [#11902] - UseIterable.forEach(Consumer)based methods, instead.- 3.15.0 - [#11902] - UseIterable.forEach(Consumer)based methods, instead.- 3.15.0 - [#11902] - UseIterable.forEach(Consumer)based methods, instead.- [#11329] - 3.15.0 - This type will be removed in the future. Do not reference it directly- 2.0.5 - Use runtime configurationSettingsinstead[#5218] - 3.14.0 - UseSelectQuery.setForLockModeNoWait()[#5218] - 3.14.0 - UseSelectQuery.setForLockModeOf(Collection)[#5218] - 3.14.0 - UseSelectQuery.setForLockModeOf(Field...)[#5218] - 3.14.0 - UseSelectQuery.setForLockModeOf(Table...)[#5218] - 3.14.0 - UseSelectQuery.setForLockModeSkipLocked()[#5218] - 3.14.0 - UseSelectQuery.setForLockModeWait(int)- [#9403] - 3.13.0 - This dialect is hardly used by anyone with jOOQ or without jOOQ and will be removed in the near future.- [#19224] - 3.21.0 - This dialect has been unsupported by the vendor and will be removed in the near future. See https://issues.apache.org/jira/browse/DERBY-7177- [#18184] - 3.21.0 - This dialect is no longer supported. If you continue to require support for H2 1.4, please get in touch here: https://github.com/jOOQ/jOOQ/issues/18184- [#17388] - 3.20.0 - This dialect is no longer supported. If you continue to require support for H2 1.4, please get in touch here: https://github.com/jOOQ/jOOQ/issues/17388- [#17388] - 3.20.0 - This dialect is no longer supported. If you continue to require support for H2 1.4, please get in touch here: https://github.com/jOOQ/jOOQ/issues/17388- [#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- [#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- [#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- [#17125] - 3.20.0 - This dialect is no longer supported. If you continue to require support for Oracle 11g, please get in touch here: https://github.com/jOOQ/jOOQ/issues/17125- [#17125] - 3.20.0 - This dialect is no longer supported. If you continue to require support for Oracle 12c, please get in touch here: https://github.com/jOOQ/jOOQ/issues/17125- [#17126] - 3.20.0 - This dialect is no longer supported. If you continue to require support for Oracle 12c, please get in touch here: https://github.com/jOOQ/jOOQ/issues/17126- [#9882] - 3.14.0 - UseSQLDialect.supportedBy(SQLDialect...)instead- 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.- 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.- 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.- 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.- 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.- 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.- 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.- 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.- 3.21.0 - [#18626] - UseTableOptions.TableType.GLOBAL_TEMPORARYorTableOptions.TableType.LOCAL_TEMPORARYinstead.- 3.21.0 - [#18626] - UseTableOptions.globalTemporaryTable()orTableOptions.localTemporaryTable()instead.- 3.21.0 - [#18626] - UseTableOptions.globalTemporaryTable(TableCommitAction).- 3.21.0 - [#18626] - UseTableOptions.globalTemporaryTable(OnCommit).- 3.15.0 - [#11898] This class will be removed in the future. Do not reuse. Data type conversion happens using internalConverterimplementations, orConverterProviderprovided ones, or implementations attached to fields via generated code, or viaField.convert(Converter), orDataType.asConvertedDataType(Converter).- 3.21.0 - [#18329] - This shaded third party dependency will be removed without replacement. Please use any other JSON parser, instead - e.g. Jackson.- 3.21.0 - [#18329] - This shaded third party dependency will be removed without replacement. Please use any other JSON parser, instead - e.g. Jackson.- 3.21.0 - [#18329] - This shaded third party dependency will be removed without replacement. Please use any other JSON parser, instead - e.g. Jackson.- 3.21.0 - [#18329] - This shaded third party dependency will be removed without replacement. Please use any other JSON parser, instead - e.g. Jackson.- 3.21.0 - [#18329] - This shaded third party dependency will be removed without replacement. Please use any other JSON parser, instead - e.g. Jackson.- 3.21.0 - [#18329] - This shaded third party dependency will be removed without replacement. Please use any other JSON parser, instead - e.g. Jackson.- 3.21.0 - [#18329] - This shaded third party dependency will be removed without replacement. Please use any other JSON parser, instead - e.g. Jackson.- 3.21.0 - [#18329] - This shaded third party dependency will be removed without replacement. Please use any other JSON parser, instead - e.g. Jackson.- [#11329] - 3.15.0 - This type will be removed in the future. Do not reference it directly- [#11329] - 3.15.0 - This type will be removed in the future. Do not reference it directly- 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 theSQLDataTypeclass has been initialised may lead to deadlocks! See https://github.com/jOOQ/jOOQ/issues/3777 for details.Use the corresponding
SQLDataTypeinstead.- 3.15.0 - [#10796] - This class will be removed, soon, no more vendor specific DSL API will be added.- 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 theSQLDataTypeclass has been initialised may lead to deadlocks! See https://github.com/jOOQ/jOOQ/issues/3777 for details.Use the corresponding
SQLDataTypeinstead.- 3.15.0 - [#10796] - This class will be removed, soon, no more vendor specific DSL API will be added.- 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 theSQLDataTypeclass has been initialised may lead to deadlocks! See https://github.com/jOOQ/jOOQ/issues/3777 for details.Use the corresponding
SQLDataTypeinstead.- 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 theSQLDataTypeclass has been initialised may lead to deadlocks! See https://github.com/jOOQ/jOOQ/issues/3777 for details.Use the corresponding
SQLDataTypeinstead.- 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 theSQLDataTypeclass has been initialised may lead to deadlocks! See https://github.com/jOOQ/jOOQ/issues/3777 for details.Use the corresponding
SQLDataTypeinstead.- 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 theSQLDataTypeclass has been initialised may lead to deadlocks! See https://github.com/jOOQ/jOOQ/issues/3777 for details.Use the corresponding
SQLDataTypeinstead.- 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 theSQLDataTypeclass has been initialised may lead to deadlocks! See https://github.com/jOOQ/jOOQ/issues/3777 for details.Use the corresponding
SQLDataTypeinstead.- 3.13.0 - [#9403] - This dialect is hardly used by anyone with jOOQ or without jOOQ and will be removed in the near future.- 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 theSQLDataTypeclass has been initialised may lead to deadlocks! See https://github.com/jOOQ/jOOQ/issues/3777 for details.Use the corresponding
SQLDataTypeinstead.- 3.15.0 - [#10796] - This class will be removed, soon, no more vendor specific DSL API will be added.- 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 theSQLDataTypeclass has been initialised may lead to deadlocks! See https://github.com/jOOQ/jOOQ/issues/3777 for details.Use the corresponding
SQLDataTypeinstead.- 3.15.0 - [#10796] - This class will be removed, soon, no more vendor specific DSL API will be added.- 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 theSQLDataTypeclass has been initialised may lead to deadlocks! See https://github.com/jOOQ/jOOQ/issues/3777 for details.Use the corresponding
SQLDataTypeinstead.- 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 theSQLDataTypeclass has been initialised may lead to deadlocks! See https://github.com/jOOQ/jOOQ/issues/3777 for details.Use the corresponding
SQLDataTypeinstead.- 3.15.0 - [#10796] - This class will be removed, soon, no more vendor specific DSL API will be added.- 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 theSQLDataTypeclass has been initialised may lead to deadlocks! See https://github.com/jOOQ/jOOQ/issues/3777 for details.Use the corresponding
SQLDataTypeinstead.- 3.15.0 - [#10796] - This class will be removed, soon, no more vendor specific DSL API will be added.- 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 theSQLDataTypeclass has been initialised may lead to deadlocks! See https://github.com/jOOQ/jOOQ/issues/3777 for details.Use the corresponding
SQLDataTypeinstead.- 3.15.0 - [#10796] - This class will be removed, soon, no more vendor specific DSL API will be added.- 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 theSQLDataTypeclass has been initialised may lead to deadlocks! See https://github.com/jOOQ/jOOQ/issues/3777 for details.Use the corresponding
SQLDataTypeinstead.- 3.15.0 - [#10796] - This class will be removed, soon, no more vendor specific DSL API will be added.- 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 theSQLDataTypeclass has been initialised may lead to deadlocks! See https://github.com/jOOQ/jOOQ/issues/3777 for details.Use the corresponding
SQLDataTypeinstead.- 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 theSQLDataTypeclass has been initialised may lead to deadlocks! See https://github.com/jOOQ/jOOQ/issues/3777 for details.Use the corresponding
SQLDataTypeinstead.- 3.15.0 - [#10796] - This class will be removed, soon, no more vendor specific DSL API will be added.- 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 theSQLDataTypeclass has been initialised may lead to deadlocks! See https://github.com/jOOQ/jOOQ/issues/3777 for details.Use the corresponding
SQLDataTypeinstead.- 3.15.0 - [#10796] - This class will be removed, soon, no more vendor specific DSL API will be added.- 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 theSQLDataTypeclass has been initialised may lead to deadlocks! See https://github.com/jOOQ/jOOQ/issues/3777 for details.Use the corresponding
SQLDataTypeinstead.- 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 theSQLDataTypeclass has been initialised may lead to deadlocks! See https://github.com/jOOQ/jOOQ/issues/3777 for details.Use the corresponding
SQLDataTypeinstead.- 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 theSQLDataTypeclass has been initialised may lead to deadlocks! See https://github.com/jOOQ/jOOQ/issues/3777 for details.Use the corresponding
SQLDataTypeinstead.- 3.15.0 - [#8611] - This function has been removed from MySQL 8- 3.15.0 - [#8611] - This function has been removed from MySQL 8- 3.15.0 - [#8611] - This function has been removed from MySQL 8- 3.15.0 - [#8611] - This function has been removed from MySQL 8- 3.15.0 - [#8611] - This function has been removed from MySQL 8- 3.15.0 - [#8611] - This function has been removed from MySQL 8- 3.15.0 - [#8611] - This function has been removed from MySQL 8- 3.15.0 - [#8611] - This function has been removed from MySQL 8- 3.15.0 - [#8611] - This function has been removed from MySQL 8- 3.15.0 - [#8611] - This function has been removed from MySQL 8- 3.15.0 - [#8611] - This function has been removed from MySQL 8- 3.15.0 - [#8611] - This function has been removed from MySQL 8- 3.15.0 - [#8611] - This function has been removed from MySQL 8- 3.15.0 - [#8611] - This function has been removed from MySQL 8- 3.15.0 - [#8611] - This function has been removed from MySQL 8- 3.15.0 - [#8611] - This function has been removed from MySQL 8- 3.15.0 - [#8611] - This function has been removed from MySQL 8- 3.15.0 - [#8611] - This function has been removed from MySQL 8- 3.15.0 - [#8611] - This function has been removed from MySQL 8- 3.15.0 - [#8611] - This function has been removed from MySQL 8- 3.15.0 - [#8611] - This function has been removed from MySQL 8- 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- 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 theSQLDataTypeclass has been initialised may lead to deadlocks! See https://github.com/jOOQ/jOOQ/issues/3777 for details.Use the corresponding
SQLDataTypeinstead.- 3.14.0 - [#8381] [#10641] - UseDSL.toChar(Field, Field)instead.- 3.14.0 - [#8381] [#10641] - UseDSL.toChar(Field, Field)instead.- 3.14.0 - [#8381] [#10641] - UseDSL.toChar(Field, Field)instead.- 3.14.0 - [#8381] [#10641] - UseDSL.toChar(Field, Field)instead.- 3.14.0 - [#8381] [#10641] - UseDSL.toChar(Field, Field)instead.- 3.14.0 - [#8381] [#10641] - UseDSL.toChar(Field, Field)instead.- 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 theSQLDataTypeclass has been initialised may lead to deadlocks! See https://github.com/jOOQ/jOOQ/issues/3777 for details.Use the corresponding
SQLDataTypeinstead.- [#12420] - 3.16.0 - Use actualOIDcolumn references in jOOQ-meta, instead.- 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 theSQLDataTypeclass has been initialised may lead to deadlocks! See https://github.com/jOOQ/jOOQ/issues/3777 for details.Use the corresponding
SQLDataTypeinstead.- 3.15.0 - [#10796] - This class will be removed, soon, no more vendor specific DSL API will be added.- 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 theSQLDataTypeclass has been initialised may lead to deadlocks! See https://github.com/jOOQ/jOOQ/issues/3777 for details.Use the corresponding
SQLDataTypeinstead.- 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 theSQLDataTypeclass has been initialised may lead to deadlocks! See https://github.com/jOOQ/jOOQ/issues/3777 for details.Use the corresponding
SQLDataTypeinstead.- 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 theSQLDataTypeclass has been initialised may lead to deadlocks! See https://github.com/jOOQ/jOOQ/issues/3777 for details.Use the corresponding
SQLDataTypeinstead.- 3.15.0 - [#10796] - This class will be removed, soon, no more vendor specific DSL API will be added.- 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 theSQLDataTypeclass has been initialised may lead to deadlocks! See https://github.com/jOOQ/jOOQ/issues/3777 for details.Use the corresponding
SQLDataTypeinstead.- 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 theSQLDataTypeclass has been initialised may lead to deadlocks! See https://github.com/jOOQ/jOOQ/issues/3777 for details.Use the corresponding
SQLDataTypeinstead.- 3.15.0 - [#10796] - This class will be removed, soon, no more vendor specific DSL API will be added.- 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 theSQLDataTypeclass has been initialised may lead to deadlocks! See https://github.com/jOOQ/jOOQ/issues/3777 for details.Use the corresponding
SQLDataTypeinstead.- 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 theSQLDataTypeclass has been initialised may lead to deadlocks! See https://github.com/jOOQ/jOOQ/issues/3777 for details.Use the corresponding
SQLDataTypeinstead.- 3.15.0 - [#10796] - This class will be removed, soon, no more vendor specific DSL API will be added.- 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 theSQLDataTypeclass has been initialised may lead to deadlocks! See https://github.com/jOOQ/jOOQ/issues/3777 for details.Use the corresponding
SQLDataTypeinstead.- [#11329] - 3.15.0 - This type will be removed in the future. Do not reference it directly- [#11329] - 3.15.0 - This type will be removed in the future. Do not reference it directly- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaWithStep.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaWithStep.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaWithStep.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaWithStep.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaWithStep.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaWithStep.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaWithStep.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaWithStep.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaWithStep.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaWithStep.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaWithStep.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaWithStep.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaWithStep.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaWithStep.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaWithStep.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaWithStep.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaWithStep.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaWithStep.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaWithStep.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaWithStep.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaWithStep.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaWithStep.mergeInto(Table)- 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.- 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 PackagesPackageDescription- 3.21.0 - [#18329] - This shaded third party dependency will be removed without replacement. Please use any other JSON parser, instead - e.g. Jackson.
-
Deprecated InterfacesInterfaceDescription- [#11329] - 3.15.0 - This type will be removed in the future. Do not reference it directly- [#11329] - 3.15.0 - This type will be removed in the future. Do not reference it directly- [#11329] - 3.15.0 - This type will be removed in the future. Do not reference it directly- [#11329] - 3.15.0 - This type will be removed in the future. Do not reference it directly- [#11329] - 3.15.0 - This type will be removed in the future. Do not reference it directly- [#11329] - 3.15.0 - This type will be removed in the future. Do not reference it directly- [#11329] - 3.15.0 - This type will be removed in the future. Do not reference it directly- [#11329] - 3.15.0 - This type will be removed in the future. Do not reference it directly- [#11329] - 3.15.0 - This type will be removed in the future. Do not reference it directly- 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.- [#11329] - 3.15.0 - This type will be removed in the future. Do not reference it directly- [#11329] - 3.15.0 - This type will be removed in the future. Do not reference it directly- [#11329] - 3.15.0 - This type will be removed in the future. Do not reference it directly- [#11329] - 3.15.0 - This type will be removed in the future. Do not reference it directly- [#11329] - 3.15.0 - This type will be removed in the future. Do not reference it directly- [#11329] - 3.15.0 - This type will be removed in the future. Do not reference it directly- [#11329] - 3.15.0 - This type will be removed in the future. Do not reference it directly- [#11329] - 3.15.0 - This type will be removed in the future. Do not reference it directly- [#11329] - 3.15.0 - This type will be removed in the future. Do not reference it directly- [#11329] - 3.15.0 - This type will be removed in the future. Do not reference it directly- [#11329] - 3.15.0 - This type will be removed in the future. Do not reference it directly- [#11329] - 3.15.0 - This type will be removed in the future. Do not reference it directly- [#11329] - 3.15.0 - This type will be removed in the future. Do not reference it directly- [#11329] - 3.15.0 - This type will be removed in the future. Do not reference it directly- [#11329] - 3.15.0 - This type will be removed in the future. Do not reference it directly- [#11329] - 3.15.0 - This type will be removed in the future. Do not reference it directly- [#11329] - 3.15.0 - This type will be removed in the future. Do not reference it directly- [#11329] - 3.15.0 - This type will be removed in the future. Do not reference it directly- 3.17.0 - [#13005] - Use
TableElementinstead.- [#11329] - 3.15.0 - This type will be removed in the future. Do not reference it directly- [#11329] - 3.15.0 - This type will be removed in the future. Do not reference it directly- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#11329] - 3.15.0 - This type will be removed in the future. Do not reference it directly- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- 3.15.0 - [#11902] - UseIterable.forEach(Consumer)based methods, instead.- [#11329] - 3.15.0 - This type will be removed in the future. Do not reference it directly- 3.21.0 - [#18566] - Do not reference this type directly.- 3.21.0 - [#18329] - This shaded third party dependency will be removed without replacement. Please use any other JSON parser, instead - e.g. Jackson.- 3.21.0 - [#18329] - This shaded third party dependency will be removed without replacement. Please use any other JSON parser, instead - e.g. Jackson.- [#11329] - 3.15.0 - This type will be removed in the future. Do not reference it directly- [#11329] - 3.15.0 - This type will be removed in the future. Do not reference it directly- [#11329] - 3.15.0 - This type will be removed in the future. Do not reference it directly- [#11329] - 3.15.0 - This type will be removed in the future. Do not reference it directly
-
Deprecated ClassesClassDescription- [#6875] [#7158] - 3.11.0 - Please re-generate your code- 3.15.0 - [#11505] - Use
Converter.ofNullable(Class, Class, Function, Function)instead, e.g.Converter.ofNullable(Date.class, LocalDate.class, Date::toLocalDate, Date::valueOf).- 3.17.0 - [#13542] - This class is no longer needed. Implement theDiagnosticsListenerSPI directly, instead.- 3.17.0 - [#13542] - This class is no longer needed. Implement theExecuteListenerSPI directly, instead.- 3.17.0 - [#13542] - This class is no longer needed. Implement theMigrationListenerSPI directly, instead.- 3.17.0 - [#13542] - This class is no longer needed. Implement theParseListenerSPI directly, instead.- 3.17.0 - [#13542] - This class is no longer needed. Implement theRecordListenerSPI directly, instead.- 3.17.0 - [#13542] - This class is no longer needed. Implement theTransactionListenerSPI directly, instead.- 3.17.0 - [#13542] - This class is no longer needed. Implement theVisitListenerSPI directly, instead.- 3.15.0 - [#11505] - UseConverter.ofNullable(Class, Class, Function, Function)instead, e.g.Converter.ofNullable(Timestamp.class, LocalDateTime.class, Timestamp::toLocalDateTime, Timestamp::valueOf).- 3.15.0 - [#11505] - UseConverter.ofNullable(Class, Class, Function, Function)instead, e.g.Converter.ofNullable(Time.class, LocalTime.class, Time::toLocalTime, Time::valueOf).- 2.0.5 - Use runtime configurationSettingsinstead- 3.15.0 - [#11898] This class will be removed in the future. Do not reuse. Data type conversion happens using internalConverterimplementations, orConverterProviderprovided ones, or implementations attached to fields via generated code, or viaField.convert(Converter), orDataType.asConvertedDataType(Converter).- 3.15.0 - [#11618] - This type is no longer used by jOOQ and will be removed in the future.- 3.15.0 - [#11618] - This type is no longer used by jOOQ and will be removed in the future.- 3.15.0 - [#11618] - This type is no longer used by jOOQ and will be removed in the future.- 3.21.0 - [#18329] - This shaded third party dependency will be removed without replacement. Please use any other JSON parser, instead - e.g. Jackson.- 3.21.0 - [#18329] - This shaded third party dependency will be removed without replacement. Please use any other JSON parser, instead - e.g. Jackson.- 3.21.0 - [#18329] - This shaded third party dependency will be removed without replacement. Please use any other JSON parser, instead - e.g. Jackson.- 3.21.0 - [#18329] - This shaded third party dependency will be removed without replacement. Please use any other JSON parser, instead - e.g. Jackson.- 3.21.0 - [#18329] - This shaded third party dependency will be removed without replacement. Please use any other JSON parser, instead - e.g. Jackson.- 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 theSQLDataTypeclass has been initialised may lead to deadlocks! See https://github.com/jOOQ/jOOQ/issues/3777 for details.Use the corresponding
SQLDataTypeinstead.- 3.15.0 - [#10796] - This class will be removed, soon, no more vendor specific DSL API will be added.- 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 theSQLDataTypeclass has been initialised may lead to deadlocks! See https://github.com/jOOQ/jOOQ/issues/3777 for details.Use the corresponding
SQLDataTypeinstead.- 3.15.0 - [#10796] - This class will be removed, soon, no more vendor specific DSL API will be added.- 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 theSQLDataTypeclass has been initialised may lead to deadlocks! See https://github.com/jOOQ/jOOQ/issues/3777 for details.Use the corresponding
SQLDataTypeinstead.- 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 theSQLDataTypeclass has been initialised may lead to deadlocks! See https://github.com/jOOQ/jOOQ/issues/3777 for details.Use the corresponding
SQLDataTypeinstead.- 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 theSQLDataTypeclass has been initialised may lead to deadlocks! See https://github.com/jOOQ/jOOQ/issues/3777 for details.Use the corresponding
SQLDataTypeinstead.- 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 theSQLDataTypeclass has been initialised may lead to deadlocks! See https://github.com/jOOQ/jOOQ/issues/3777 for details.Use the corresponding
SQLDataTypeinstead.- 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 theSQLDataTypeclass has been initialised may lead to deadlocks! See https://github.com/jOOQ/jOOQ/issues/3777 for details.Use the corresponding
SQLDataTypeinstead.- 3.13.0 - [#9403] - This dialect is hardly used by anyone with jOOQ or without jOOQ and will be removed in the near future.- 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 theSQLDataTypeclass has been initialised may lead to deadlocks! See https://github.com/jOOQ/jOOQ/issues/3777 for details.Use the corresponding
SQLDataTypeinstead.- 3.15.0 - [#10796] - This class will be removed, soon, no more vendor specific DSL API will be added.- 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 theSQLDataTypeclass has been initialised may lead to deadlocks! See https://github.com/jOOQ/jOOQ/issues/3777 for details.Use the corresponding
SQLDataTypeinstead.- 3.15.0 - [#10796] - This class will be removed, soon, no more vendor specific DSL API will be added.- 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 theSQLDataTypeclass has been initialised may lead to deadlocks! See https://github.com/jOOQ/jOOQ/issues/3777 for details.Use the corresponding
SQLDataTypeinstead.- 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 theSQLDataTypeclass has been initialised may lead to deadlocks! See https://github.com/jOOQ/jOOQ/issues/3777 for details.Use the corresponding
SQLDataTypeinstead.- 3.15.0 - [#10796] - This class will be removed, soon, no more vendor specific DSL API will be added.- 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 theSQLDataTypeclass has been initialised may lead to deadlocks! See https://github.com/jOOQ/jOOQ/issues/3777 for details.Use the corresponding
SQLDataTypeinstead.- 3.15.0 - [#10796] - This class will be removed, soon, no more vendor specific DSL API will be added.- 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 theSQLDataTypeclass has been initialised may lead to deadlocks! See https://github.com/jOOQ/jOOQ/issues/3777 for details.Use the corresponding
SQLDataTypeinstead.- 3.15.0 - [#10796] - This class will be removed, soon, no more vendor specific DSL API will be added.- 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 theSQLDataTypeclass has been initialised may lead to deadlocks! See https://github.com/jOOQ/jOOQ/issues/3777 for details.Use the corresponding
SQLDataTypeinstead.- 3.15.0 - [#10796] - This class will be removed, soon, no more vendor specific DSL API will be added.- 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 theSQLDataTypeclass has been initialised may lead to deadlocks! See https://github.com/jOOQ/jOOQ/issues/3777 for details.Use the corresponding
SQLDataTypeinstead.- 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 theSQLDataTypeclass has been initialised may lead to deadlocks! See https://github.com/jOOQ/jOOQ/issues/3777 for details.Use the corresponding
SQLDataTypeinstead.- 3.15.0 - [#10796] - This class will be removed, soon, no more vendor specific DSL API will be added.- 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 theSQLDataTypeclass has been initialised may lead to deadlocks! See https://github.com/jOOQ/jOOQ/issues/3777 for details.Use the corresponding
SQLDataTypeinstead.- 3.15.0 - [#10796] - This class will be removed, soon, no more vendor specific DSL API will be added.- 3.8.0 - [#4550] Do not reference this type directly.- 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 theSQLDataTypeclass has been initialised may lead to deadlocks! See https://github.com/jOOQ/jOOQ/issues/3777 for details.Use the corresponding
SQLDataTypeinstead.- 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 theSQLDataTypeclass has been initialised may lead to deadlocks! See https://github.com/jOOQ/jOOQ/issues/3777 for details.Use the corresponding
SQLDataTypeinstead.- 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 theSQLDataTypeclass has been initialised may lead to deadlocks! See https://github.com/jOOQ/jOOQ/issues/3777 for details.Use the corresponding
SQLDataTypeinstead.- 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 theSQLDataTypeclass has been initialised may lead to deadlocks! See https://github.com/jOOQ/jOOQ/issues/3777 for details.Use the corresponding
SQLDataTypeinstead.- 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 theSQLDataTypeclass has been initialised may lead to deadlocks! See https://github.com/jOOQ/jOOQ/issues/3777 for details.Use the corresponding
SQLDataTypeinstead.- 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 theSQLDataTypeclass has been initialised may lead to deadlocks! See https://github.com/jOOQ/jOOQ/issues/3777 for details.Use the corresponding
SQLDataTypeinstead.- 3.15.0 - [#10796] - This class will be removed, soon, no more vendor specific DSL API will be added.- 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 theSQLDataTypeclass has been initialised may lead to deadlocks! See https://github.com/jOOQ/jOOQ/issues/3777 for details.Use the corresponding
SQLDataTypeinstead.- 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 theSQLDataTypeclass has been initialised may lead to deadlocks! See https://github.com/jOOQ/jOOQ/issues/3777 for details.Use the corresponding
SQLDataTypeinstead.- 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 theSQLDataTypeclass has been initialised may lead to deadlocks! See https://github.com/jOOQ/jOOQ/issues/3777 for details.Use the corresponding
SQLDataTypeinstead.- 3.15.0 - [#10796] - This class will be removed, soon, no more vendor specific DSL API will be added.- 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 theSQLDataTypeclass has been initialised may lead to deadlocks! See https://github.com/jOOQ/jOOQ/issues/3777 for details.Use the corresponding
SQLDataTypeinstead.- 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 theSQLDataTypeclass has been initialised may lead to deadlocks! See https://github.com/jOOQ/jOOQ/issues/3777 for details.Use the corresponding
SQLDataTypeinstead.- 3.15.0 - [#10796] - This class will be removed, soon, no more vendor specific DSL API will be added.- 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 theSQLDataTypeclass has been initialised may lead to deadlocks! See https://github.com/jOOQ/jOOQ/issues/3777 for details.Use the corresponding
SQLDataTypeinstead.- 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 theSQLDataTypeclass has been initialised may lead to deadlocks! See https://github.com/jOOQ/jOOQ/issues/3777 for details.Use the corresponding
SQLDataTypeinstead.- 3.15.0 - [#10796] - This class will be removed, soon, no more vendor specific DSL API will be added.- 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 theSQLDataTypeclass has been initialised may lead to deadlocks! See https://github.com/jOOQ/jOOQ/issues/3777 for details.Use the corresponding
SQLDataTypeinstead.
-
Deprecated Enum ClassesEnum ClassDescription- 3.11.0 - [#7258] - This part of the
VisitListenerSPI 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- UseLog.Levelinstead
-
Deprecated Exception ClassesException ClassDescription- [#12425] - 3.16.0 - Missing implementations should be added as soon as possible!- 3.21.0 - [#18329] - This shaded third party dependency will be removed without replacement. Please use any other JSON parser, instead - e.g. Jackson.
-
Deprecated Annotation InterfacesAnnotation InterfaceDescription- 3.17.0 - [#13071] - Use
ApiStatus.Internalinstead.
-
Deprecated FieldsFieldDescription- use #expiration instead
-
Deprecated MethodsMethodDescription- 3.14.0 - [#9911] - This method is no longer supported.- 3.14.0 - [#9911] - This method is no longer supported.- 3.14.0 - [#9911] - This method is no longer supported.- 3.12.0 - [#5909] - Use
RenderKeywordCaseinstead.- 3.12.0 - [#5909] - UseRenderQuotedNamesandRenderNameCaseinstead.- 3.18.0 - [#14634] - The configuration of this transformation is deprecated. It will no longer be commercially available only, but apply also to the jOOQ Open Source Edition, when required.- 3.18.0 - [#13912] [#15316] - UseSettings.fetchTriggerValuesAfterReturninginstead.- 3.18.0 - [#13912] [#15316] - UseSettings.fetchTriggerValuesAfterReturninginstead.- 3.12.0 - [#5909] - UseRenderKeywordCaseinstead.- 3.12.0 - [#5909] - UseRenderQuotedNamesandRenderNameCaseinstead.- 3.18.0 - [#14634] - The configuration of this transformation is deprecated. It will no longer be commercially available only, but apply also to the jOOQ Open Source Edition, when required.- 3.18.0 - [#13912] [#15316] - UseSettings.fetchTriggerValuesAfterReturninginstead.- 3.12.0 - [#5909] - UseRenderKeywordCaseinstead.- 3.12.0 - [#5909] - UseRenderQuotedNamesandRenderNameCaseinstead.- 3.18.0 - [#14634] - The configuration of this transformation is deprecated. It will no longer be commercially available only, but apply also to the jOOQ Open Source Edition, when required.- 2.0.5 - UseConfiguration.settings()instead- [#10317] - 3.14.0 - Do not reuse this method. It will be removed without replacement.- [#10317] - 3.14.0 - Do not reuse this method. It will be removed without replacement.- [#10689] - 3.14.0 - This converter does not work. Do not use this method, useConverters.identity(Class)instead.- [#10689] - 3.14.0 - This method does not provide any useful functionality and will be removed in the future.- 3.15.0 - [#11902] - UseIterable.forEach(Consumer)based methods, instead.- 3.15.0 - [#11902] - UseIterable.forEach(Consumer)based methods, instead.- 3.20.0 - [#16810] - Static data type conversion has been a controversial historic feature of jOOQ. While occasionally useful for internal data types (such asStringtoIntegerconversion, etc.) it doesn't work well with user defined types. 1) This method does not go throughConfiguration.converterProvider(), 2) nor does it provide an appropriateConverterContextto aContextConverter, leading to subtle bugs. 3) It also doesn't make any guarantees related to what user defined types can be passed to it. This is why this method is deprecated and will be removed in a future jOOQ version. UseDataType.getConverter()on this type, instead, and use that for data type conversions.- 3.20.0 - [#16810] - Static data type conversion has been a controversial historic feature of jOOQ. While occasionally useful for internal data types (such asStringtoIntegerconversion, etc.) it doesn't work well with user defined types. 1) This method does not go throughConfiguration.converterProvider(), 2) nor does it provide an appropriateConverterContextto aContextConverter, leading to subtle bugs. 3) It also doesn't make any guarantees related to what user defined types can be passed to it. This is why this method is deprecated and will be removed in a future jOOQ version. UseDataType.getConverter()on this type, instead, and use that for data type conversions.- 3.20.0 - [#16810] - Static data type conversion has been a controversial historic feature of jOOQ. While occasionally useful for internal data types (such asStringtoIntegerconversion, etc.) it doesn't work well with user defined types. 1) This method does not go throughConfiguration.converterProvider(), 2) nor does it provide an appropriateConverterContextto aContextConverter, leading to subtle bugs. 3) It also doesn't make any guarantees related to what user defined types can be passed to it. This is why this method is deprecated and will be removed in a future jOOQ version. UseDataType.getConverter()on this type, instead, and use that for data type conversions.- 3.21.0 - [#18732] - UseDataType.isQualifiedRecord()instead, orDataType.isUDTRecord()if that's more precise.- [#6280] - 3.10 - Do not reuse this method. It will be completely internal with jOOQ 4.0- 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.- 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.- 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.- 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.- 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.- 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.- 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.- 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.- 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.- 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.- 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.- 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.- 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.- 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.- 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.- 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.- 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.- 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.- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#6280] - 3.10 - Do not reuse this method. It will be completely internal with jOOQ 4.0- 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.- 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.- 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.- 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.- 3.11 - [#7538] - UseDSL.abs(Field)instead.- 3.11 - [#7538] - UseDSL.acos(Field)instead.- 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.- 3.13 - [#9407] - UseDSL.ascii(Field)instead.- 3.11 - [#7538] - UseDSL.asin(Field)instead.- 3.11 - [#7538] - UseDSL.atan(Field)instead.- 3.11 - [#7538] - UseDSL.atan2(Field, Number)instead.- 3.11 - [#7538] - UseDSL.atan2(Field, Field)instead.- 3.11 - [#7538] - UseDSL.avg(Field)instead.- 3.11 - [#7538] - UseDSL.avg(Field)instead.- 3.13 - [#9407] - UseDSL.bitLength(Field)instead.- 3.11 - [#7538] - UseDSL.ceil(Field)instead.- [#12494] - 3.20.0 - UseField.touched(Record)instead.- 3.13 - [#9407] - UseDSL.charLength(Field)instead.- 3.13 - [#9407] - UseDSL.coalesce(Field, Field...)instead.- 3.13 - [#9407] - UseDSL.coalesce(Object, Object...)instead.- 3.11 - [#7538] - UseDSL.cos(Field)instead.- 3.11 - [#7538] - UseDSL.cosh(Field)instead.- 3.11 - [#7538] - UseDSL.cot(Field)instead.- 3.11 - [#7538] - UseDSL.coth(Field)instead.- 3.11 - [#7538] - UseDSL.count(Field)instead.- 3.11 - [#7538] - UseDSL.countDistinct(Field)instead.- 3.11 - [#7538] - UseDSL.count(Field)instead.- 3.13 - [#9407] - UseDSL.decode(Field, Field, Field)instead.- 3.13 - [#9407] - UseDSL.decode(Field, Field, Field, Field...)instead.- 3.13 - [#9407] - UseDSL.decode(Object, Object, Object)instead.- 3.13 - [#9407] - UseDSL.decode(Object, Object, Object, Object...)instead.- 3.11 - [#7538] - UseDSL.deg(Field)instead.- 3.11 - [#7538] - UseDSL.exp(Field)instead.- 3.11 - [#7538] - UseDSL.extract(Field, DatePart)instead.- 3.11 - [#7538] - UseDSL.firstValue(Field)instead.- 3.11 - [#7538] - UseDSL.floor(Field)instead.- 3.11 - [#7538] - UseDSL.greatest(Field, Field...)instead.- 3.11 - [#7538] - UseDSL.greatest(Field, Field...)instead.- 3.11 - [#7538] - UseDSL.lag(Field)instead.- 3.11 - [#7538] - UseDSL.lag(Field, int)instead.- 3.11 - [#7538] - UseDSL.lag(Field, int, Field)instead.- 3.11 - [#7538] - UseDSL.lag(Field, int, Object)instead.- 3.11 - [#7538] - UseDSL.lastValue(Field)instead.- 3.11 - [#7538] - UseDSL.lead(Field)instead.- 3.11 - [#7538] - UseDSL.lead(Field, int)instead.- 3.11 - [#7538] - UseDSL.lead(Field, int, Field)instead.- 3.11 - [#7538] - UseDSL.lead(Field, int, Object)instead.- 3.11 - [#7538] - UseDSL.least(Field, Field...)instead.- 3.11 - [#7538] - UseDSL.least(Field, Field...)instead.- 3.13 - [#9407] - UseDSL.length(Field)instead.- 3.11 - [#7538] - UseDSL.ln(Field)instead.- 3.11 - [#7538] - UseDSL.log(Field, int)instead.- 3.13 - [#9407] - UseDSL.lower(Field)instead.- 3.13 - [#9407] - UseDSL.lpad(Field, int)instead.- 3.13 - [#9407] - UseDSL.lpad(Field, int, char)instead.- 3.13 - [#9407] - UseDSL.lpad(Field, Field)instead.- 3.13 - [#9407] - UseDSL.lpad(Field, Field, Field)instead.- 3.13 - [#9407] - UseDSL.ltrim(Field)instead.- 3.11 - [#7538] - UseDSL.max(Field)instead.- 3.11 - [#7538] - UseDSL.max(Field)instead.- 3.11 - [#7538] - UseDSL.median(Field)instead.- 3.11 - [#7538] - UseDSL.min(Field)instead.- 3.11 - [#7538] - UseDSL.min(Field)instead.- 3.13 - [#9407] - UseDSL.nullif(Field, Field)instead.- 3.13 - [#9407] - UseDSL.nullif(Field, Object)instead.- 3.13 - [#9407] - UseDSL.nvl(Field, Field)instead.- 3.13 - [#9407] - UseDSL.nvl(Field, Object)instead.- 3.13 - [#9407] - UseDSL.nvl2(Field, Field, Field)instead.- 3.13 - [#9407] - UseDSL.nvl2(Field, Object, Object)instead.- 3.13 - [#9407] - UseDSL.octetLength(Field)instead.- 3.13 - [#9407] - UseDSL.position(Field, String)instead.- 3.13 - [#9407] - UseDSL.position(Field, Field)instead.- 3.11 - [#7538] - UseDSL.rad(Field)instead.- 3.13 - [#9407] - UseDSL.repeat(Field, int)instead.- 3.13 - [#9407] - UseDSL.repeat(Field, Field)instead.- 3.13 - [#9407] - UseDSL.replace(Field, String)instead.- 3.13 - [#9407] - UseDSL.replace(Field, String, String)instead.- 3.13 - [#9407] - UseDSL.replace(Field, Field)instead.- 3.13 - [#9407] - UseDSL.replace(Field, Field, Field)instead.- 3.11 - [#7538] - UseDSL.round(Field)instead.- 3.11 - [#7538] - UseDSL.round(Field, int)instead.- 3.13 - [#9407] - UseDSL.rpad(Field, int)instead.- 3.13 - [#9407] - UseDSL.rpad(Field, int, char)instead.- 3.13 - [#9407] - UseDSL.rpad(Field, Field)instead.- 3.13 - [#9407] - UseDSL.rpad(Field, Field, Field)instead.- 3.13 - [#9407] - UseDSL.rtrim(Field)instead.- 3.11 - [#7538] - UseDSL.sign(Field)instead.- 3.11 - [#7538] - UseDSL.sin(Field)instead.- 3.11 - [#7538] - UseDSL.sinh(Field)instead.- 3.11 - [#7538] - UseDSL.sqrt(Field)instead.- 3.11 - [#7538] - UseDSL.stddevPop(Field)instead.- 3.11 - [#7538] - UseDSL.stddevPop(Field)instead.- 3.11 - [#7538] - UseDSL.stddevSamp(Field)instead.- 3.11 - [#7538] - UseDSL.stddevSamp(Field)instead.- 3.13 - [#9407] - UseDSL.substring(Field, int)instead.- 3.13 - [#9407] - UseDSL.substring(Field, int, int)instead.- 3.13 - [#9407] - UseDSL.substring(Field, Field)instead.- 3.13 - [#9407] - UseDSL.substring(Field, Field, Field)instead.- 3.11 - [#7538] - UseDSL.sum(Field)instead.- 3.11 - [#7538] - UseDSL.sum(Field)instead.- 3.11 - [#7538] - UseDSL.tan(Field)instead.- 3.11 - [#7538] - UseDSL.tanh(Field)instead.- 3.13 - [#9407] - UseDSL.trim(Field)instead.- 3.13 - [#9407] - UseDSL.upper(Field)instead.- 3.11 - [#7538] - UseDSL.varPop(Field)instead.- 3.11 - [#7538] - UseDSL.varPop(Field)instead.- 3.11 - [#7538] - UseDSL.varSamp(Field)instead.- 3.11 - [#7538] - UseDSL.varSamp(Field)instead.- 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.- 3.21.0 - [#19250] - This method will be removed in the future. Please use one of the alternative XML formatting methods, instead.- 3.21.0 - [#19250] - This method will be removed in the future. Please use one of the alternative XML formatting methods, instead.- [#6875] [#7158] - 3.11.0 - Please re-generate your code- [#6875] [#7158] - 3.11.0 - Please re-generate your code- [#6875] [#7158] - 3.11.0 - Please re-generate your code- [#6875] [#7158] - 3.11.0 - Please re-generate your code- [#6875] [#7158] - 3.11.0 - Please re-generate your code- [#6875] [#7158] - 3.11.0 - Please re-generate your code- Please, re-generate your routine code.- Please, re-generate your routine code.- Please, re-generate your routine code.- Please, re-generate your routine code.- Please, re-generate your routine code.- Please, re-generate your routine code.- Please, re-generate your routine code.- Please, re-generate your routine code.- Please, re-generate your routine code.- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDefaultDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDefaultDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDefaultDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDefaultDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDefaultDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDefaultDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDefaultDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDefaultDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDefaultDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDefaultDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDefaultDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDefaultDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDefaultDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDefaultDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDefaultDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDefaultDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDefaultDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDefaultDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDefaultDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDefaultDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDefaultDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDefaultDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDefaultDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDefaultDSLContext.mergeInto(Table)- 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.- 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.- 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.- 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.- 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.- 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.- 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.- 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.- 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.- 3.11.0 - [#7483] - The (indirect) use of the internal static data type registry is not recommended.- [#7956] - 3.12.0 - UseDSL.groupConcat(Field)andGroupConcatSeparatorStep.separator(String)instead.- [#15196] - 3.19.0 - The semantics of theFieldarguments in this method is inconsistent with that of other overloads, such asDSL.jsonbObject(Field, Field), which can lead to subtle bugs. Please refrain from using this overload as it will be removed in the future. UseDSL.jsonObject(JSONEntry...)instead.- [#15196] - 3.19.0 - The semantics of theFieldarguments in this method is inconsistent with that of other overloads, such asDSL.jsonbObject(Field, Field), which can lead to subtle bugs. Please refrain from using this overload as it will be removed in the future. UseDSL.jsonObject(JSONEntry...)instead.- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSL.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSL.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSL.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSL.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSL.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSL.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSL.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSL.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSL.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSL.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSL.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSL.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSL.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSL.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSL.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSL.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSL.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSL.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSL.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSL.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSL.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSL.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSL.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSL.mergeInto(Table)- [#11092] - 3.15.0 - This method will be removed without public replacement.- [#11092] - 3.15.0 - This method will be removed without public replacement.- [#11092] - 3.15.0 - This method will be removed without public replacement.- [#11092] - 3.15.0 - This method will be removed without public replacement.- [#11092] - 3.15.0 - This method will be removed without public replacement.- [#11092] - 3.15.0 - This method will be removed without public replacement.- [#11092] - 3.15.0 - This method will be removed without public replacement.- [#11812] - 3.15.0 - UseRow1as aSelectFielddirectly, instead.- [#11812] - 3.15.0 - UseRow10as aSelectFielddirectly, instead.- [#11812] - 3.15.0 - UseRow11as aSelectFielddirectly, instead.- [#11812] - 3.15.0 - UseRow12as aSelectFielddirectly, instead.- [#11812] - 3.15.0 - UseRow13as aSelectFielddirectly, instead.- [#11812] - 3.15.0 - UseRow14as aSelectFielddirectly, instead.- [#11812] - 3.15.0 - UseRow15as aSelectFielddirectly, instead.- [#11812] - 3.15.0 - UseRow16as aSelectFielddirectly, instead.- [#11812] - 3.15.0 - UseRow17as aSelectFielddirectly, instead.- [#11812] - 3.15.0 - UseRow18as aSelectFielddirectly, instead.- [#11812] - 3.15.0 - UseRow19as aSelectFielddirectly, instead.- [#11812] - 3.15.0 - UseRow2as aSelectFielddirectly, instead.- [#11812] - 3.15.0 - UseRow20as aSelectFielddirectly, instead.- [#11812] - 3.15.0 - UseRow21as aSelectFielddirectly, instead.- [#11812] - 3.15.0 - UseRow22as aSelectFielddirectly, instead.- [#11812] - 3.15.0 - UseRow3as aSelectFielddirectly, instead.- [#11812] - 3.15.0 - UseRow4as aSelectFielddirectly, instead.- [#11812] - 3.15.0 - UseRow5as aSelectFielddirectly, instead.- [#11812] - 3.15.0 - UseRow6as aSelectFielddirectly, instead.- [#11812] - 3.15.0 - UseRow7as aSelectFielddirectly, instead.- [#11812] - 3.15.0 - UseRow8as aSelectFielddirectly, instead.- [#11812] - 3.15.0 - UseRow9as aSelectFielddirectly, instead.- [#11812] - 3.15.0 - UseRowNas aSelectFielddirectly, instead.- 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.- 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.- 3.20.0 - [#15723] - Regenerate your code.- 3.20.0 - [#15723] - Regenerate your code.- 3.20.0 - [#15723] - Regenerate your code.- 3.20.0 - [#15723] - Regenerate your code.- 3.20.0 - [#9736] - Regenerate your code.- 3.20.0 - [#9736] - Regenerate your code.- 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.- 3.14.0 - [#9404] - Please re-generate your code.- 3.14.0 - [#9404] - Please re-generate your code.- 3.21.0 - [#19044] - UseInternal.createParameter(String, DataType, boolean)instead.- 3.21.0 - [#19044] - UseInternal.createParameter(String, DataType, boolean, Binding)instead.- 3.21.0 - [#19044] - UseInternal.createParameter(String, DataType, boolean, Converter)instead.- 3.21.0 - [#19044] - UseInternal.createParameter(String, DataType, boolean, Converter, Binding)instead.- 3.20.0 - [#15723] - Regenerate your code.- 3.20.0 - [#15723] - Regenerate your code.- 3.14.0 - [#9404] - Please re-generate your code.- 3.14.0 - [#9404] - Please re-generate your code.- [#11058] - 3.14.5 - Please re-generate your code.- [#12238] - 3.16.0 - Please re-generate your code.- 3.21.0 - [#18684] - UseQOM.CommentOn.$objectType()instead.- 3.21.0 - [#18684] - UseQOM.CommentOn.$objectType()instead.- 3.21.0 - [#18684] - UseQOM.CommentOn.$objectType()instead.- 3.21.0 - [#18684] - UseQOM.CommentOn.$objectType()instead.- 3.21.0 - [#18603] - UseQOM.CreateTable.$tableScope()instead.- 3.21.0 - [#18603] - UseQOM.CreateTable.$tableScope()instead.- 3.21.0 - [#18603] - UseQOM.DropTable.$tableScope()instead.- 3.21.0 - [#18603] - UseQOM.DropTable.$tableScope()instead.- 3.21.0 - [#19277] - UseQOM.MultisetAgg.$fields()instead.- 3.12.0 - [#8000] - UseUDTImpl.createField(Name, DataType, UDT)instead.- 3.12.0 - [#8000] - UseUDTImpl.createField(Name, DataType, UDT, String)instead.- 3.12.0 - [#8000] - UseUDTImpl.createField(Name, DataType, UDT, String, Binding)instead.- 3.12.0 - [#8000] - UseUDTImpl.createField(Name, DataType, UDT, String, Converter)instead.- 3.12.0 - [#8000] - UseUDTImpl.createField(Name, DataType, UDT, String, Converter, Binding)instead.- 3.14.0 - [#10010] - UseLoaderCSVStep.fieldsCorresponding()instead.- 3.14.0 - [#10010] - UseLoaderJSONStep.fieldsCorresponding()instead.- 3.14.0 - [#4941] - UseLoaderListenerStep.onRowEnd(LoaderRowListener)instead.- 3.14.0 - [#10010] - UseLoaderRowsStep.fieldsCorresponding()instead.- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaDSLContext.mergeInto(Table)- 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.- 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.- 3.12.0 - [#8163] - UsePivotForStep.for_(Field)instead.- CallingQueryPartInternal.accept(Context)directly on aQueryPartis almost always a mistake. Instead,Context.visit(QueryPart)should be called.- CallingQueryPartInternal.rendersContent(Context)directly on aQueryPartis almost always a mistake.- [#12494] - 3.20.0 - UseRecord.touched()instead.- [#12494] - 3.20.0 - UseRecord.touched(boolean)instead.- [#12494] - 3.20.0 - UseRecord.touched(int)instead.- [#12494] - 3.20.0 - UseRecord.touched(int, boolean)instead.- [#12494] - 3.20.0 - UseRecord.touched(String)instead.- [#12494] - 3.20.0 - UseRecord.touched(String, boolean)instead.- [#12494] - 3.20.0 - UseRecord.touched(Field)instead.- [#12494] - 3.20.0 - UseRecord.touched(Field, boolean)instead.- [#12494] - 3.20.0 - UseRecord.touched(Name)instead.- [#12494] - 3.20.0 - UseRecord.touched(Name, boolean)instead.- 3.15.0 - [#11902] - UseIterable.forEach(Consumer)based methods, instead.- 3.15.0 - [#11902] - UseIterable.forEach(Consumer)based methods, instead.- [#7461] - SEEK BEFORE is not implemented correctly- [#7461] - SEEK BEFORE is not implemented correctly[#5218] - 3.14.0 - UseSelectQuery.setForLockModeNoWait()[#5218] - 3.14.0 - UseSelectQuery.setForLockModeOf(Collection)[#5218] - 3.14.0 - UseSelectQuery.setForLockModeOf(Field...)[#5218] - 3.14.0 - UseSelectQuery.setForLockModeOf(Table...)[#5218] - 3.14.0 - UseSelectQuery.setForLockModeSkipLocked()[#5218] - 3.14.0 - UseSelectQuery.setForLockModeWait(int)- [#7461] - SEEK BEFORE is not implemented correctly- [#7461] - SEEK BEFORE is not implemented correctly- [#7461] - SEEK BEFORE is not implemented correctly- [#7461] - SEEK BEFORE is not implemented correctly- [#7461] - SEEK BEFORE is not implemented correctly- [#7461] - SEEK BEFORE is not implemented correctly- [#7461] - SEEK BEFORE is not implemented correctly- [#7461] - SEEK BEFORE is not implemented correctly- [#7461] - SEEK BEFORE is not implemented correctly- [#7461] - SEEK BEFORE is not implemented correctly- [#7461] - SEEK BEFORE is not implemented correctly- [#7461] - SEEK BEFORE is not implemented correctly- [#7461] - SEEK BEFORE is not implemented correctly- [#7461] - SEEK BEFORE is not implemented correctly- [#7461] - SEEK BEFORE is not implemented correctly- [#7461] - SEEK BEFORE is not implemented correctly- [#7461] - SEEK BEFORE is not implemented correctly- [#7461] - SEEK BEFORE is not implemented correctly- [#7461] - SEEK BEFORE is not implemented correctly- [#7461] - SEEK BEFORE is not implemented correctly- [#7461] - SEEK BEFORE is not implemented correctly- [#7461] - SEEK BEFORE is not implemented correctly- [#7461] - SEEK BEFORE is not implemented correctly- [#7461] - SEEK BEFORE is not implemented correctly- [#7461] - SEEK BEFORE is not implemented correctly- [#7461] - SEEK BEFORE is not implemented correctly- [#7461] - SEEK BEFORE is not implemented correctly- [#7461] - SEEK BEFORE is not implemented correctly- [#7461] - SEEK BEFORE is not implemented correctly- [#7461] - SEEK BEFORE is not implemented correctly- [#7461] - SEEK BEFORE is not implemented correctly- [#7461] - SEEK BEFORE is not implemented correctly- [#7461] - SEEK BEFORE is not implemented correctly- [#7461] - SEEK BEFORE is not implemented correctly- [#7461] - SEEK BEFORE is not implemented correctly- [#7461] - SEEK BEFORE is not implemented correctly- [#7461] - SEEK BEFORE is not implemented correctly- [#7461] - SEEK BEFORE is not implemented correctly- [#7461] - SEEK BEFORE is not implemented correctly- [#7461] - SEEK BEFORE is not implemented correctly- [#7461] - SEEK BEFORE is not implemented correctly- [#7461] - SEEK BEFORE is not implemented correctly- [#7461] - SEEK BEFORE is not implemented correctly- [#7461] - SEEK BEFORE is not implemented correctly- [#7461] - SEEK BEFORE is not implemented correctly- [#7461] - SEEK BEFORE is not implemented correctly- [#9882] - 3.14.0 - UseSQLDialect.supportedBy(SQLDialect...)instead- 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.- 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.- 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.- 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.- 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.- 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.- 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.- 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.- 3.21.0 - [#18626] - UseTableOptions.globalTemporaryTable()orTableOptions.localTemporaryTable()instead.- 3.21.0 - [#18626] - UseTableOptions.globalTemporaryTable(TableCommitAction).- 3.21.0 - [#18626] - UseTableOptions.globalTemporaryTable(OnCommit).- UseMockFileDatabaseConfiguration.nullLiteral(String)instead.- Experimental: Do not use. Subject to change.[#78] 0.9.11, useReflect.onClass(Class)instead.[#78] 0.9.11, useReflect.onClass(String)instead.[#78] 0.9.11, useReflect.onClass(String, ClassLoader)instead.- 3.15.0 - [#8611] - This function has been removed from MySQL 8- 3.15.0 - [#8611] - This function has been removed from MySQL 8- 3.15.0 - [#8611] - This function has been removed from MySQL 8- 3.15.0 - [#8611] - This function has been removed from MySQL 8- 3.15.0 - [#8611] - This function has been removed from MySQL 8- 3.15.0 - [#8611] - This function has been removed from MySQL 8- 3.15.0 - [#8611] - This function has been removed from MySQL 8- 3.15.0 - [#8611] - This function has been removed from MySQL 8- 3.15.0 - [#8611] - This function has been removed from MySQL 8- 3.15.0 - [#8611] - This function has been removed from MySQL 8- 3.15.0 - [#8611] - This function has been removed from MySQL 8- 3.15.0 - [#8611] - This function has been removed from MySQL 8- 3.15.0 - [#8611] - This function has been removed from MySQL 8- 3.15.0 - [#8611] - This function has been removed from MySQL 8- 3.15.0 - [#8611] - This function has been removed from MySQL 8- 3.15.0 - [#8611] - This function has been removed from MySQL 8- 3.15.0 - [#8611] - This function has been removed from MySQL 8- 3.15.0 - [#8611] - This function has been removed from MySQL 8- 3.15.0 - [#8611] - This function has been removed from MySQL 8- 3.15.0 - [#8611] - This function has been removed from MySQL 8- 3.15.0 - [#8611] - This function has been removed from MySQL 8- 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- 3.14.0 - [#8381] [#10641] - UseDSL.toChar(Field, Field)instead.- 3.14.0 - [#8381] [#10641] - UseDSL.toChar(Field, Field)instead.- 3.14.0 - [#8381] [#10641] - UseDSL.toChar(Field, Field)instead.- 3.14.0 - [#8381] [#10641] - UseDSL.toChar(Field, Field)instead.- 3.14.0 - [#8381] [#10641] - UseDSL.toChar(Field, Field)instead.- 3.14.0 - [#8381] [#10641] - UseDSL.toChar(Field, Field)instead.- 3.18.0 - [#14388] - UseDSL.arrayAppend(Field, Field)instead.- 3.18.0 - [#14388] - UseDSL.arrayAppend(Field, Object)instead.- 3.18.0 - [#14388] - UseDSL.arrayAppend(Object[], Field)instead.- 3.18.0 - [#14388] - UseDSL.arrayAppend(Object[], Object)instead.- 3.18.0 - [#14388] - UseDSL.arrayConcat(Field, Field)instead.- 3.18.0 - [#14388] - UseDSL.arrayConcat(Field, Object[])instead.- 3.18.0 - [#14388] - UseDSL.arrayConcat(Object[], Field)instead.- 3.18.0 - [#14388] - UseDSL.arrayConcat(Object[], Object[])instead.- 3.18.0 - [#14352] - UseDSL.arrayOverlap(Field, Field)instead.- 3.18.0 - [#14352] - UseDSL.arrayOverlap(Field, Object[])instead.- 3.16.0 - [#14352] - UseDSL.arrayOverlap(Object[], Field)instead.- 3.18.0 - [#14352] - UseDSL.arrayOverlap(Object[], Object[])instead.- 3.18.0 - [#14388] - UseDSL.arrayPrepend(Field, Field)instead.- 3.18.0 - [#14388] - UseDSL.arrayPrepend(Field, Object[])instead.- 3.18.0 - [#14388] - UseDSL.arrayPrepend(Object, Field)instead.- 3.18.0 - [#14388] - UseDSL.arrayPrepend(Object, Object[])instead.- 3.18.0 - [#14388] - UseDSL.arrayRemove(Field, Field)instead.- 3.18.0 - [#14388] - UseDSL.arrayRemove(Field, Object)instead.- 3.18.0 - [#14388] - UseDSL.arrayRemove(Object[], Field)instead.- 3.18.0 - [#14388] - UseDSL.arrayRemove(Object[], Object)instead.- 3.18.0 - [#11981] - UseDSL.arrayReplace(Field, Field, Field)instead.- 3.18.0 - [#11981] - UseDSL.arrayReplace(Field, Field, Field)instead.- 3.18.0 - [#11981] - UseDSL.arrayReplace(Field, Field, Field)instead.- 3.18.0 - [#11981] - UseDSL.arrayReplace(Object[], Object, Object)instead.- [#12420] - 3.16.0 - Use actualOIDcolumn references in jOOQ-meta, instead.- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaWithStep.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaWithStep.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaWithStep.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaWithStep.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaWithStep.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaWithStep.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaWithStep.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaWithStep.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaWithStep.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaWithStep.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaWithStep.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaWithStep.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaWithStep.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaWithStep.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaWithStep.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaWithStep.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaWithStep.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaWithStep.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaWithStep.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaWithStep.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaWithStep.mergeInto(Table)- [#10045] - 3.14.0 - Use the standard SQL MERGE API instead, viaWithStep.mergeInto(Table)- 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.- 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 ConstructorsConstructorDescription- 3.20.0 - [#15723] - Re-generate your code.- 3.20.0 - [#15723] - Re-generate your code.- 3.20.0 - [#15723] - Re-generate your code.- 3.20.0 - [#15723] - Re-generate your code.- 3.20.0 - [#15723] - Re-generate your code.- 3.20.0 - [#15723] - Re-generate your code.- 3.20.0 - [#15723] - Re-generate your code.- 3.20.0 - [#15723] - Re-generate your code.- 3.20.0 - [#15723] - Re-generate your code.- 3.20.0 - [#15723] - Re-generate your code.- 3.21.0 - [#19125] - This class will be removed from public API, do not reuse.- 3.11 - [#6631] - Use
DefaultBinding.binding(Converter)instead.- [#11058] - 3.14.5 - Please re-generate your code.- [#11058] - 3.14.5 - Please re-generate your code.- [#8012] - 3.19.0 - Please re-generate your code.- [#13639] [#14985] [#15005] - 3.19.0 - Please re-generate your code.- [#13639] [#14985] [#15005] - 3.19.0 - Please re-generate your code.- 3.11 - [#7027] - UseTableImpl(Name, Schema, Table, Field[], Comment)instead.- [#13639] [#14985] [#15005] - 3.19.0 - Please re-generate your code.- [#15583] - 3.19.0 - Please re-generate your code.- [#15583] - 3.19.0 - Please re-generate your code.- [#15583] - 3.19.0 - Please re-generate your code.- [#15050] - 3.19.0 - Do not construct your own logger. UseJooqLogger.getLogger(Class)methods instead.
-
Deprecated Enum ConstantsEnum ConstantDescription- [#9403] - 3.13.0 - This dialect is hardly used by anyone with jOOQ or without jOOQ and will be removed in the near future.- [#19224] - 3.21.0 - This dialect has been unsupported by the vendor and will be removed in the near future. See https://issues.apache.org/jira/browse/DERBY-7177- [#18184] - 3.21.0 - This dialect is no longer supported. If you continue to require support for H2 1.4, please get in touch here: https://github.com/jOOQ/jOOQ/issues/18184- [#17388] - 3.20.0 - This dialect is no longer supported. If you continue to require support for H2 1.4, please get in touch here: https://github.com/jOOQ/jOOQ/issues/17388- [#17388] - 3.20.0 - This dialect is no longer supported. If you continue to require support for H2 1.4, please get in touch here: https://github.com/jOOQ/jOOQ/issues/17388- [#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- [#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- [#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- [#17125] - 3.20.0 - This dialect is no longer supported. If you continue to require support for Oracle 11g, please get in touch here: https://github.com/jOOQ/jOOQ/issues/17125- [#17125] - 3.20.0 - This dialect is no longer supported. If you continue to require support for Oracle 12c, please get in touch here: https://github.com/jOOQ/jOOQ/issues/17125- [#16628] - 3.20.0 - Use
SQLDialect.ORACLE23AIinstead.- [#17126] - 3.20.0 - This dialect is no longer supported. If you continue to require support for Oracle 12c, please get in touch here: https://github.com/jOOQ/jOOQ/issues/17126- 3.21.0 - [#18626] - UseTableOptions.TableType.GLOBAL_TEMPORARYorTableOptions.TableType.LOCAL_TEMPORARYinstead.