Hello Martin, There had been a significant change to jOOQ's internals with respect to how Converters are passed around. The change was tracked as issue #3233: https://github.com/jOOQ/jOOQ/issues/3233
In order to better help you assess what might have been going wrong for you between 3.3.1 and 3.4.4, I would probably need an example of how you implemented that custom DataType. Best Regards, Lukas 2014-11-10 17:48 GMT+01:00 Martin Karsten < [email protected]>: > We were trying to upgrade from the free version of JooQ 3.3.1 to the > commercial version of JooQ 3.4.4. Our code uses custom datatypes for our > tables, which worked just fine under 3.3.1, but afte the upgrade the > converter methods aren't called anymore and our Insert-Statements fail > because the default converters can't convert the values we're giving them > right. > > > We are registering our custom datatypes by implementing the DataType > interface and then creating the field objects via the > AbstractTable.createField method, into which we feed our DataType objects. > > We are using jooQ in a Scala environment. > > Does anybody have a clue what might have changed between Versions 3.3.1 > and 3.4.4 that might have caused this failure? > > Thanks in advance, Martin Karsten. > > -- > 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]. > For more options, visit https://groups.google.com/d/optout. > -- 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]. For more options, visit https://groups.google.com/d/optout.
