[
https://issues.apache.org/jira/browse/OPENJPA-3028?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18138842#comment-18138842
]
ASF subversion and git services commented on OPENJPA-3028:
----------------------------------------------------------
Commit 5f4b6ec268ab12600064f6bb7f5727b86b39f72b in openjpa's branch
refs/heads/OPENJPA-3028-derby-extract-week from Richard Zowalla
[ https://gitbox.apache.org/repos/asf?p=openjpa.git;h=5f4b6ec26 ]
[OPENJPA-3028] Extract the ISO week on Derby
Derby has no function for the week of the year and TIMESTAMPDIFF counts
in the JVM time zone, so EXTRACT(WEEK) was rejected. Compute the
ISO-8601 week from YEAR, MONTH and DAY with integer arithmetic in the
proleptic Gregorian calendar, which works in every clause and does not
depend on the time zone.
> Jakarta Persistence 3.2 TCK failures on Derby, MySQL and SQL Server
> -------------------------------------------------------------------
>
> Key: OPENJPA-3028
> URL: https://issues.apache.org/jira/browse/OPENJPA-3028
> Project: OpenJPA
> Issue Type: Epic
> Reporter: Richard Zowalla
> Assignee: Richard Zowalla
> Priority: Major
> Attachments: run_de.tar.xz, run_ms.tar.xz, run_my.tar.xz,
> run_or.tar.xz
>
>
> Results of the Jakarta Persistence 3.2 TCK with
> {{openjpa-integration/tck/run-tck32.sh}} (reported by Maxim Solodovnik on
> dev@):
> * PostgreSQL 16: passed
> * MySQL 8.4.8: 2134 tests, 43 errors
> * SQL Server 2017-CU12: 2134 tests, 45 errors
> * Derby: 2134 tests, 184 errors
> The sub-tasks group the errors by cause. Several groups show up on more than
> one database. Where the TCK output only says "<test> failed", the cause still
> has to be found from the TCK logs.
> Note: the TCK build does not work with Maven 3.10.0; 3.9.x works.
--
This message was sent by Atlassian Jira
(v10.3.26#10030026)
