I've made some progress with defining a binding for TIMESTAMPZ <->
Instant but there's one aspect of the code generation I don't seem to
be able to control:
/**
* The column <code>SUBSCRIPTIONS.Z.DATEZ</code>.
*/
public final TableField<ZRecord, Instant> DATEZ = createField("DATEZ",
org.jooq.impl.SQLDataType.TIMESTAMPWITHTIMEZONE.nullable(false), this,
"", new InstantBinding());
The generator correctly sets the type bound for the column, but
somewhere it has a registry that infuses the TIMESTAMPWITHTIMEZONE
type, but the mapping for this is DataType<OffsetDateTime>.
Is there a way to coerce the field to be DateType<Instant> ?
On Tue, Dec 22, 2015 at 5:02 PM, Ben Hood <0x6e6...@gmail.com> wrote:
> On Tue, Dec 22, 2015 at 4:53 PM, Lukas Eder <lukas.e...@gmail.com> wrote:
>> Interesting, I wasn't aware of this. Do you have a link?
>
> https://tonyhasler.wordpress.com/2010/09/04/tonys-tirade-against-timestamp-with-time-zone/
>
> This appears to have written in the context of 10g - it's difficult to
> tell whether the limitations apply to 12c.
--
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 jooq-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
