Hi Robert, Thanks for your message. Where did you upgrade from? And what's your configuration for <javaTimeTypes/>? Note that <dateAsTimestamp/> is there to indicate that (mostly Oracle's) DATE types should be generated as TIMESTAMP types.
We've added JSR-310 support in jOOQ 3.9. The data type TIMESTAMP WITH TIME ZONE is now mapped to OffsetDateTime. It was erroneously mapped to Timestamp before that, although before supporting Java 8 and JSR-310, there wasn't really any good alternative. You can always make use of <forcedType/> to rewrite data types for any columns: https://www.jooq.org/doc/latest/manual/code-generation/codegen-advanced/codegen-config-forced-types I hope this helps Lukas 2017-10-04 15:20 GMT+02:00 Robert Mattler <[email protected]>: > Upgraded to 3.10 and the code generation is creating > > private OffsetDateTime createdOn; > > > This breaks everything in the front end application since it doesn't know > how to handle OffsetDateTime. > > > Added dateAsTimestamp but this effected the dates. Just want the > timestamps back. Thanks in advance. > > > <configuration> > <generator> > <database> > <dateAsTimestamp>true</dateAsTimestamp> > </database> > </generator></configuration> > > > Using PostgreSQL 9.6.2. > > -- > 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.
