public final Class SQLDataType

The Types#BIGINT type.

The unsigned Types#BIGINT type.

The Types#BINARY type.

The Types#BIT type.

The Types#BLOB type.

The Types#BOOLEAN type.

The Types#CHAR type.

The Types#CLOB type.

The Types#DATE type.

The Types#DECIMAL type.

The zero-scale Types#DECIMAL type.

The Types#DOUBLE type.

The Types#FLOAT type.

The Geography type.

This is not a JDBC standard. This type handles spatial types where they are supported.

If you want to opt out of code generation support for this type, you can specify /configuration/generator/generate/spatialTypes to false.

This data type is supported only by the commercial editions of jOOQ.

The Geometry type.

This is not a JDBC standard. This type handles spatial types where they are supported.

If you want to opt out of code generation support for this type, you can specify /configuration/generator/generate/spatialTypes to false.

This data type is supported only by the commercial editions of jOOQ.

A Types#TIMESTAMP_WITH_TIMEZONE type that uses UTC as time zone.

Neither JDBC, nor most SQL databases support the INSTANT data type, which is often the only kind of timestamp which can be expected to behave across all server and client time zone settings. This implementation is backed by the database vendor's TIMESTAMP WITH TIME ZONE data type implementation, which may (e.g. Oracle) or may not (e.g. PostgreSQL) store the timestamp information. Irrespective of that storage, this type will always produce time zone agnostic instants in client code.

The Types#INTEGER type.

The unsigned Types#INTEGER type.

A vendor specific INTERVAL YEAR TO SECOND data type, which combines INTERVALYEARTOMONTH and INTERVALDAYTOSECOND.

If you want to opt out of code generation support for this type, you can specify /configuration/generator/generate/intervalTypes to false.

The SQL standard INTERVAL DAY TO SECOND data type.

If you want to opt out of code generation support for this type, you can specify /configuration/generator/generate/intervalTypes to false.

The SQL standard INTERVAL YEAR TO MONTH data type.

If you want to opt out of code generation support for this type, you can specify /configuration/generator/generate/intervalTypes to false.

The JSON type.

This is not a JDBC standard. This type handles JSON types where they are supported.

If you want to opt out of code generation support for this type, you can specify /configuration/generator/generate/jsonTypes to false.

The JSONB type.

This is not a JDBC standard. This type handles JSONB types where they are supported.

If you want to opt out of code generation support for this type, you can specify /configuration/generator/generate/jsonTypes to false.

The Types#DATE type.

The Types#TIMESTAMP type.

The Types#TIME type.

The Types#LONGNVARCHAR type.

The Types#LONGVARBINARY type.

The Types#LONGVARCHAR type.

The Types#NCHAR type.

The Types#NCLOB type.

The Types#NUMERIC type.

The Types#NVARCHAR type.

The Types#TIMESTAMP_WITH_TIMEZONE type.

The behaviour of this data type is influenced by the JDBC driver and the database that is used. Some databases support actual time zones (as in ZonedDateTime), other databases support only offsets (as in OffsetDateTime). Some databases retain the actual time zone information that is stored and reproduce it with every fetch (e.g. SQLDialect#ORACLE), others use this type as a synonym for a timestamp in UTC (e.g. SQLDialect#POSTGRES), producing possibly a value in the current time zone of the database or the client. Please refer to your database for more information about the behaviour of this data type.

The Types#TIME_WITH_TIMEZONE type.

The behaviour of this data type is influenced by the JDBC driver and the database that is used. Some databases support actual time zones (as in ZonedDateTime), other databases support only offsets (as in OffsetDateTime). Some databases retain the actual time zone information that is stored and reproduce it with every fetch (e.g. SQLDialect#ORACLE), others use this type as a synonym for a timestamp in UTC (e.g. SQLDialect#POSTGRES), producing possibly a value in the current time zone of the database or the client. Please refer to your database for more information about the behaviour of this data type.

The Types#OTHER type.

The Types#REAL type.

The Types#STRUCT type.

The ResultSet type.

This is not a JDBC standard. This type emulates REF CURSOR types and similar constructs

The Types#ROWID type.

The Types#SMALLINT type.

The unsigned Types#SMALLINT type.

The Types#TIME type.

The Types#TIMESTAMP type.

The Types#TIMESTAMP_WITH_TIMEZONE type.

An alias for OFFSETDATETIME

The Types#TIME_WITH_TIMEZONE type.

An alias for OFFSETTIME

The Types#TINYINT type.

The unsigned Types#TINYINT type.

The UUID type.

This is not a JDBC standard. This type handles UUID types where they are supported

The Types#VARBINARY type.

The Types#VARCHAR type.

The XML type.

This is not a JDBC standard. This type handles XML types where they are supported.

If you want to opt out of code generation support for this type, you can specify /configuration/generator/generate/xmlTypes to false.

A Types#SMALLINT type that represents a year.

While JDBC does not support this type, some dialects do, specifically those of the SQLDialectCategory#MYSQL category.