Am Fr., 8. Juni 2018 um 13:03 Uhr schrieb Beldrew <[email protected]>:
> Oh you might want to highlight "#7419 Rename jooq-meta and jooq-codegen > packages to avoid conflicts in JPMS" a bit more, had to go look up the new > packages for JavaGenerator and my db dialect (mysql) in GitHub. Not hard > but being my first jooq upgrade it threw me for a bit. > Thanks for the hint. That's a good idea. I'll look into it - this can be improved both in the release notes and in the error message that is displayed when the old package names are used. I've created an issue for this: https://github.com/jOOQ/jOOQ/issues/7556 > And one quick question about 3.11.0 #6627 Add DateToLocalDateConverter, > TimeToLocalTimeConverter, TimestampToLocalDateTimeConverter: does this > 'fix' mysql Date column being offset by a day? Or is this a JPA issues > like google searches suggest tho why the JPA is applying time zone > information to a column type that doesn't have one is beyond me... I'm at > the point where I'll probably change it to a datetime field just to have > timezone info so I can make sure it stays as UTC. > I'm sorry, I'm not quite sure what you mean. Would you mind being a bit more specific? Do note: For future visitors, it will be very helpful if there was only one discussion per topic. It will be much easier to track down individual topics and read only what's relevant in any given context. Thanks, Lukas -- 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.
