Hi Denis, Thank you for your enquiry and for your additional feedback. jOOQ's internals are ready for JSR-310 types, i.e. they can correctly bind java.time.* values to JDBC statements, and fetch them from ResultSets (give or take the usual bugs for new functionality).
However, we have not yet proceeded with implementing https://github.com/jOOQ/jOOQ/issues/4429 as you've noticed - i.e. source code generation support for JSR-310 types - for several reasons: - We don't want to make those the default (yet) - Much of jOOQ's API in org.jooq.impl.DSL expects some Field<? extends java.util.Date> types, e.g. timestampDiff. Because we cannot overload these functions based on their generic argument types due to generic type erasure, we need to re-think our source code generation strategy in this area. We're in a bit of a catch 22 situation here. Without JSR-310, we cannot support TIMESTAMP WITH TIME ZONE types for those databases that have the type. With JSR-310, we'll break existing jOOQ API. I'm hoping that we'll find a solution for jOOQ 3.8. Until then, you can always use converters, as you did. I hope this explanation helps. Of course, we're very open to suggestions, as we might have missed something... Best Regards, Lukas 2015-10-10 10:37 GMT+02:00 Denis Miorandi <[email protected]>: > This worked for me inside generator/database tag of generator > configuration. You have to write your own converter foreach type. > > <customTypes> > <customType> > <name>LocalDateTime</name> > <type>java.util.time.LocalDateTime</type> > > <converter>base.config.jooq.converters.LocalDateTimeConverter</converter> > </customType> > <customType> > <name>LocalDate</name> > <type>java.util.time.LocalDate</type> > > <converter>base.config.jooq.converters.LocalDateConverter</converter> > </customType> > <customType> > <name>LocalTime</name> > <type>java.util.time.LocalTime</type> > > <converter>base.config.jooq.converters.LocalTimeConverter</converter> > </customType></customTypes><forcedTypes> > <forcedType> > <name>LocalDateTime</name> > > <expression>(\w+\.)?(?!UDT_PREFIX|PROC_PREFIX)\w+(\.\w+)?</expression> > <types>DATETIME</types> > </forcedType> > <forcedType> > <name>LocalTime</name> > > <expression>(\w+\.)?(?!UDT_PREFIX|PROC_PREFIX)\w+(\.\w+)?</expression> > <types>TIME</types> > </forcedType> > <forcedType> > <name>LocalDate</name> > > <expression>(\w+\.)?(?!UDT_PREFIX|PROC_PREFIX)\w+(\.\w+)?</expression> > <types>DATE</types> > </forcedType></forcedTypes> > > > > > Il giorno sabato 10 ottobre 2015 09:47:34 UTC+2, Denis Miorandi ha scritto: >> >> Reading this https://github.com/jOOQ/jOOQ/issues/4429, I found that this >> addition is related to runtime. It seems >> that for generator we need to wait 3.8. >> >> >> >> Il giorno venerdì 9 ottobre 2015 19:46:45 UTC+2, Denis Miorandi ha >> scritto: >>> >>> Does anyone used Java 8 LocalTime, LocalDate or LocalDateTime? >>> My configuration is based on >>> >>> - sqlserver 2012 express >>> - jdbc 4.2 driver from Ms. (I don't know if is mandatory for JSR310 >>> in jooq) >>> - Java8 compiled version of jooq pro 3.7.0 >>> - JDK 1.8.0_60 >>> >>> I expect to have sql types automatically mapped on java jrs310 types on >>> generation but it doesn't. Actually my results are >>> >>> - sql datetime ==> java.sql.TimeStamp >>> - sql date ==> Long >>> - sql time ==> java.sql.Time >>> >>> Am I missing something? >>> >>> Tks >>> >>> Denis >>> >>> >>> -- > 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.
