[
https://issues.apache.org/jira/browse/OPENJPA-2940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18080577#comment-18080577
]
ASF subversion and git services commented on OPENJPA-2940:
----------------------------------------------------------
Commit 76e8293934d8d2ed9ba84cfbf925c8c091b15f64 in openjpa's branch
refs/heads/OPENJPA-2940 from Richard Zowalla
[ https://gitbox.apache.org/repos/asf?p=openjpa.git;h=76e829393 ]
[OPENJPA-2940] Request 6 fractional digits for temporal @Version columns
Instant, LocalDateTime, Date, and Calendar version columns left column
precision unset, producing DATETIME(0) on MariaDB/MySQL by default. Two
updates within the same whole second stored identical versions, defeating
optimistic locking. Request 6 fractional digits (microseconds) in
ColumnVersionStrategy.map() for temporal javaTypes when the user has not
already specified precision. DATETIME(6) / TIMESTAMP(6) matches what
Derby/PostgreSQL already use.
> Implement Jakarta Persistence 3.2
> ---------------------------------
>
> Key: OPENJPA-2940
> URL: https://issues.apache.org/jira/browse/OPENJPA-2940
> Project: OpenJPA
> Issue Type: Improvement
> Reporter: Paulo Cristovão de Araújo Silva Filho
> Priority: Major
> Attachments: image-2026-03-28-14-55-26-463.png
>
>
> Implement Jakarta Persistence API 3.2 as prescribed by
> [specification|https://jakarta.ee/specifications/persistence/3.2/] and
> required by Jakarta EE 11.
> This change requires JDK17 or higher compatibility and needs considerable
> checks.
> I've already pushed a branch (WIP) without the proper API bump, focusing on
> updating dependencies while keeping the project passing its current tests at
> least in default profile.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
