I upgrade our internal setup to use Jooq 3.10.6 and now I'm getting a
different behavior for the date and time fields.
What used to be a java.sql.timestamp is now being generated
as OffsetDateTime.
I'm going from 3.9.0 to 3.10.6.
The previous config was as follows.
<generate>
<pojos>true</pojos>
<pojosEqualsAndHashCode>true</pojosEqualsAndHashCode>
<interfaces>true</interfaces>
<!-- Brings in JSR-308 adding compile time checks for
@NotNull and @Size checks -->
<validationAnnotations>true</validationAnnotations>
<!-- Gives preference for java.time rather then relying on
java.sql.timestamp breaking change -->
<!-- We really should take the time to migrate to this
feature. -->* <javaTimeTypes>false</javaTimeTypes>
* </generate>
My understand was that *javaTimeTypes *should turn off any java 8 date
times which includes OffsetDateTime.
--
Thank you
Samir Faci
https://keybase.io/csgeek
--
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.
