>
> That's fair enough but I would like to get a clearer picture of what is
> and isn't converted to Java 8 object.  for example, why is the behavior for
> datetime with timezone not consistent with timestamp with timezone.
>

What database is this? Can you provide an example in DDL?


> If i set the flag javaTimeTypes to false I would expect that no java 8
> time object would be used.
>

Indeed, it is debatable whether the meaning of this flag should be:

- Do not use the JSR-310 types *at all*
- Do not use the JSR-310 types, where a viable alternative in JDBC is
available (e.g. java.sql.Timestamp)

The latter was implemented, and this is confusing a few people. I have
created an issue to fix this:
https://github.com/jOOQ/jOOQ/issues/7126

It's important to understand that binding java.sql.Timestamp to a TIMESTAMP
WITH TIME ZONE data type in the database is not correct. It may work if
client and server are both in the same time zone, but otherwise, there is
no way for jOOQ (or any JDBC client) to guarantee the fetched timestamp (as
in Timestamp.getTime()) is really the correct timestamp. Prior to jOOQ 3.9,
this may have simply "worked" (and failed silently).


> If that's not the case.. (which is a judgement call on your part that
> you're completely entitled to do) but I would like to know though which
> objects are used and not used when we set that flag to false.
>

False currently means: "Use JDBC types rather than JSR 310 types, if such a
type is available". This includes java.sql.Timestamp, java.sql.Time,
java.sql.Date. But not java.time.OffsetDateTime and java.time.OffsetTime.

My take is if we set javaTimeTypes = false then my expectations was that
> any class in java.time would not be used, if that's not the case we should
> document that somewhere.
>

Yes.

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