New versions: Dev (3.15) | Latest (3.14) | 3.13 | 3.12 | 3.11 | 3.10 | 3.9 | 3.8 | Old versions: 3.7 | 3.6 | 3.5 | 3.4 | 3.3 | 2.6

Custom data types and type conversion

Applies to ✅ Open Source Edition   ✅ Express Edition   ✅ Professional Edition   ✅ Enterprise Edition

When using a custom type in jOOQ, you need to let jOOQ know about its associated org.jooq.Converter. Ad-hoc usages of such converters has been discussed in the chapter about data type conversion. A more common use-case, however, is to let jOOQ know about custom types at code generation time. Use the following configuration elements to specify, that you'd like to use GregorianCalendar for all database fields that start with DATE_OF_

  <!-- First, register your custom types here -->
      <!-- Specify the fully-qualified class name of your custom type -->

      <!-- Associate that custom type with your converter. Note, a
           custom type can only have one converter in jOOQ -->

  <!-- Then, associate custom types with database columns -->
      <!-- Specify again he fully-qualified class name of your custom type -->

      <!-- Add a list of comma-separated regular expressions matching columns -->

The above configuration will lead to AUTHOR.DATE_OF_BIRTH being generated like this:

public class TAuthor extends UpdatableTableImpl<TAuthorRecord> {

    // [...]
    public final TableField<TAuthorRecord, GregorianCalendar> DATE_OF_BIRTH =    // [...]
    // [...]


This means that the bound type of <T> will be GregorianCalendar, wherever you reference DATE_OF_BIRTH. jOOQ will use your custom converter when binding variables and when fetching data from java.util.ResultSet:

// Get all date of births of authors born after 1980
List<GregorianCalendar> result =
      .where( GregorianCalendar(1980, 0, 1)))


Do you have any feedback about this page? We'd love to hear it!

The jOOQ Logo