You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cayenne.apache.org by "Nikita Timofeev (Jira)" <ji...@apache.org> on 2026/08/18 08:38:03 UTC

[jira] [Updated] (CAY-2881) Switch to standard JDBC approach to read/write java.time classes

     [ https://issues.apache.org/jira/browse/CAY-2881?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Nikita Timofeev updated CAY-2881:
---------------------------------
    Fix Version/s: 5.0-M3
                       (was: 5.0-M2)

> Switch to standard JDBC approach to read/write java.time classes
> ----------------------------------------------------------------
>
>                 Key: CAY-2881
>                 URL: https://issues.apache.org/jira/browse/CAY-2881
>             Project: Cayenne
>          Issue Type: Improvement
>            Reporter: Andrus Adamchik
>            Priority: Minor
>             Fix For: 5.0-M3
>
>
> On most databases, we no longer need ValueObjectTypes for java.time classes, as demonstrated by CAY-2701 for modern MySQL (also see https://dev.mysql.com/blog-archive/support-for-date-time-types-in-connector-j-8-0/ ) :
> {noformat}
> rs.getObject(i, LocalDateTime.class);
> st.setObject(pos, val, type);
> {noformat}
> So let's make the approach in CAY-2701 the default in Cayenne, creating the appropriate ExtendedTypes, and then check which databases DO NOT support it, and create custom ExtendedTypes for those. 
> Of course, as a result MySQLLocalDateTimeType will no longer be needed, superseded by  the standard one.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)