2018-05-08 16:55 GMT+02:00 Ben Hood <[email protected]>: > I think I might have solved the issue by putting > > SET TIME ZONE ‘UTC’; > > into the connection pool init and then at runtime by supplying an > OffsetDateTime. > > But it would be to good to get the OffsetDateTime code generation working, > instead of mapping to Object. > > Can this be done with a converter, or does it require a full binding?
You can use a Converter, risking that the type jOOQ is getting back from ResultSet.getObject() is not the correct type, and risking that jOOQ will not bind variables correctly, because it does not really know how to bind Object types (e.g. what casts might be needed) Use a Binding if you want to be sure. Or just use the data type rewriting feature to tell jOOQ that the type is really TIMESTAMP WITH TIME ZONE. This is the least work for you. -- 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.
