3

I am using JPADatabase to generate JOOQ classes from my existing JPA entites. From manual, I know that JPADatabase internally uses H2 database to read the meta data schema and generate the code. Due to H2 database has no data type for Numeric, instead it has Decimal. Therefore all my numeric data type are converted to SQLDataType.DECIMAL.

public final TableField<MyTableRecord, BigDecimal> NUM_FIELD = createField(DSL.name("NUM_FIELD"), SQLDataType.DECIMAL, this, "");

I even try to use forcedType to force generate the SQLDataType.NUMERIC when running the code gen, but the result still shows SQLDataType.DECIMAL. And I found it even works for Double, if I put SQLDataType.DOUBLE in the forcedType, but just not work for SQLDataType.NUMERIC.

<forcedTypes>
                    <forcedType>
                      <name>NUMERIC</name>
                      <includeExpression>.*\.num_field</includeExpression>
                      <includeTypes>.*</includeTypes>
                      <nullability>ALL</nullability>
                      <objectType>ALL</objectType>
                    </forcedType>
                  </forcedTypes>

Is there any way to make JPADatabase code gen to produce SQLDataType.NUMERIC?

Chris Lee
  • 67
  • 2

1 Answers1

0

In most dialects, the distinction between DECIMAL and NUMERIC shouldn't matter, especially when you generate client code from pre-existing DDL statements. The client logic to bind variables of types DECIMAL and NUMERIC is almost the same in jOOQ.

The reason why your forced type was likely not applied is because the regular expressions are case sensitive. As your generated code shows, the column is called NUM_FIELD (in upper case). One way to solve this is by making your regex case insensitive:

<includeExpression>(?i:.*\.num_field)</includeExpression>
Lukas Eder
  • 211,314
  • 129
  • 689
  • 1,509
  • Hi Lukas, thanks for your answer. It's really helpful. One another thing I would like to know is what's the usage or purpose to have SQLDataType with each generated field? Since we already have a return type and client code is likely to use the this type to do the compile check. Why we still need to know the actual SQLDataType in generated class/fields? – Chris Lee Nov 11 '20 at 05:53
  • @ChrisLee: I'll be very happy to answer this as a new question – Lukas Eder Nov 11 '20 at 06:34
  • no problem. I ask the question here https://stackoverflow.com/questions/64788481/whats-the-usage-of-fields-sqldatatype-in-jooqs-auto-generated-classes – Chris Lee Nov 11 '20 at 14:36