[
https://issues.apache.org/jira/browse/OPENJPA-3028?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18139652#comment-18139652
]
ASF subversion and git services commented on OPENJPA-3028:
----------------------------------------------------------
Commit 3b725ec26c25f16f1ea175212f9b4f228d9b8b5c in openjpa's branch
refs/heads/OPENJPA-3028-oracle-unittests from Richard Zowalla
[ https://gitbox.apache.org/repos/asf?p=openjpa.git;h=3b725ec26 ]
[OPENJPA-3028] Load COALESCE, CASE and NULLIF of a java.sql.Date or Time as such
The Oracle driver returns a Timestamp for a DATE column, which also holds
java.sql.Date and java.sql.Time fields. Selecting COALESCE or CASE over
such a field loaded the value with getObject and converted it to the type
of the field, which failed on Oracle with "ClassCastException: Cannot
convert object ... of type class java.sql.Timestamp into an instance of
class java.sql.Date".
COALESCE, CASE and NULLIF expressions of type java.sql.Date or
java.sql.Time are now read with ResultSet.getDate and getTime, so the
driver does the conversion. Such queries now return a java.sql.Date or
java.sql.Time on Oracle, as on the other databases. Expressions of any
other type are read with getObject as before, and Filters.convert is
unchanged.
> 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)
