Actually, I found another thread that's referring to the exact issue I'm
running into.

https://groups.google.com/forum/#!topic/jooq-user/qawy4ijgHqk

I tried the regex specified and that didn't work for me.


>From what I can see something along these lines should work based on Lukas'
suggestion.  Though I'm still getting a OffsetDateTime being generated.


<forcedTypes>

   <forcedType>
        <name>TIMESTAMP</name>
         <!-- 
<expression>created_on|last_modified_on|fax_response_time|effective_date|assigned_on|transaction_posted_date|transaction_created_date|transaction_deposit_date|time_stamp|created_date</expression>
-->
        <types>(?i:timestamp with time zone)</types>
  </forcedType>
</forcedTypes>

​



My take is that if we are forcing the code generation to NOT use Java 8
date/time objects then we should not have the code generate any objects
that imports java.time which should include the OffsetDateTime.

I'm trying to understand if the JavaTimeType is deprecated or if there is
only a certain subset of classes that are supported.




On Mon, Apr 2, 2018 at 10:18 AM, Samir Faci <[email protected]> wrote:

> 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
>



-- 
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.

Reply via email to