Hi Clément, Great to hear your tests are running!
On Tue, Sep 15, 2020 at 5:50 PM Clément Allain <[email protected]> wrote: > Thanks for your answers, it now builds, runs and passes all our > integrations tests! > > I tried to reproduce the misleading "Unused forcedType" INFO log by > creating few tables with different kind of columns, but failed, look like > it's not that easy.. > There isn't any redundant forcedType configuration in our work project > either, but a complex and old database on which we used liquibase to > generate a legacy changelog.xml years ago to start using liquibase. > If you think of any hints, I could give it another try. > Well, if you have time to use a debugger on this, you could place some breakpoints, e.g. on AbstractDatabase.markUsed(ForcedType): https://github.com/jOOQ/jOOQ/blob/version-3.13.4/jOOQ-meta/src/main/java/org/jooq/meta/AbstractDatabase.java#L1334 And AbstractDatabase.getConfiguredForcedType(Definition definition, DataTypeDefinition definedType) https://github.com/jOOQ/jOOQ/blob/version-3.13.4/jOOQ-meta/src/main/java/org/jooq/meta/AbstractDatabase.java#L1690 Both in jOOQ-meta. You can debug the code generator using mvnDebug. > About H2, thank you for noticing, I didn't check the issue today. For H2 > future upgrade, the dependency is managed by Spring Boot, I hope it won't > break our build some day. > I wouldn't bet on it. H2 2.0 seems to be quite backwards incompatible in many subtle ways. We'll try to get a release out on our side as quickly as possible once they release H2 2.0. Until then, I think it's best to postpone this upgrade for critical projects. -- You received this message because you are subscribed to the Google Groups "jOOQ User Group" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jooq-user/CAB4ELO4whD%2BkNz54F2CRCNwmChpt7_ToUyXTQZqdODRu1cjOxg%40mail.gmail.com.
