You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@openjpa.apache.org by "Maxim Solodovnik (Jira)" <ji...@apache.org> on 2026/09/12 13:40:00 UTC

[jira] [Resolved] (OPENJPA-2969) Instant.now() precision loss on DB round-trip

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

Maxim Solodovnik resolved OPENJPA-2969.
---------------------------------------
    Resolution: Fixed

> Instant.now() precision loss on DB round-trip
> ---------------------------------------------
>
>                 Key: OPENJPA-2969
>                 URL: https://issues.apache.org/jira/browse/OPENJPA-2969
>             Project: OpenJPA
>          Issue Type: Sub-task
>          Components: jpa
>    Affects Versions: 4.2.0
>            Reporter: Maxim Solodovnik
>            Assignee: Maxim Solodovnik
>            Priority: Major
>             Fix For: 4.2.0
>
>
> Discussion thread: https://github.com/apache/openjpa/pull/144#discussion_r3683003132
> **(medium)** `Instant.now()` carries micro/nano precision on modern JVMs; if the version column's precision is lower (MySQL TIMESTAMP defaults, Oracle DATE) the value read back differs from the in-memory version, producing spurious optimistic-lock failures on the next flush - the same reason TimestampVersionStrategy deliberately uses millisecond granularity. Should this truncate to a precision known to survive the DB round-trip?



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