[
https://issues.apache.org/jira/browse/OPENJPA-2940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18080579#comment-18080579
]
ASF subversion and git services commented on OPENJPA-2940:
----------------------------------------------------------
Commit c938650a998282ae40b44793857c298d5a0b69b3 in openjpa's branch
refs/heads/OPENJPA-2940 from Richard Zowalla
[ https://gitbox.apache.org/repos/asf?p=openjpa.git;h=c938650a9 ]
[OPENJPA-2940] Enable microsecond temporal precision on modern MariaDB/MySQL
MariaDB >= 10.2 and MySQL >= 5.7 support fractional-second precision on
DATETIME/TIME columns. Bump dateFractionDigits to 6 inside the existing
version-gated block so temporal columns use DATETIME(6)/TIME(6) by default.
This fixes optimistic-locking on @Version Instant/LocalDateTime columns
where two updates within the same whole second otherwise stored identical
versions. Matches PostgreSQL and Derby defaults.
> 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)
