[
https://issues.apache.org/jira/browse/OPENJPA-3055?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18136383#comment-18136383
]
ASF subversion and git services commented on OPENJPA-3055:
----------------------------------------------------------
Commit bd8ccd3b9af64b36240af908f2603a3f0f8ec483 in openjpa's branch
refs/heads/OPENJPA-3055 from Richard Zowalla
[ https://gitbox.apache.org/repos/asf?p=openjpa.git;h=bd8ccd3b9 ]
[OPENJPA-3055] Keep the fraction of a second in EXTRACT(SECOND) on MySQL and
MariaDB
EXTRACT(SECOND) on MySQL and MariaDB returns the whole seconds only. Add
EXTRACT(MICROSECOND) / 1000000.0 to keep the fraction, as OPENJPA-3041 did
for H2. A LocalTime parameter also lost its fraction, because it was bound
as a java.sql.Time; bind and read it as a LocalTime instead.
> EXTRACT(SECOND) lost the fraction (all MySQL and MariaDB jobs)
> --------------------------------------------------------------
>
> Key: OPENJPA-3055
> URL: https://issues.apache.org/jira/browse/OPENJPA-3055
> Project: OpenJPA
> Issue Type: Bug
> Reporter: Richard Zowalla
> Assignee: Richard Zowalla
> Priority: Major
> Fix For: 4.2.0
>
>
> - MySQL and MariaDB return only whole seconds for EXTRACT(SECOND). The fix
> adds EXTRACT(MICROSECOND)/1000000.0, the same approach OPENJPA-3041 used for
> H2.
> - A second cause turned up after that: LocalTime parameters were sent to
> the database as java.sql.Time, which has no fraction of a second. Both
> dictionaries now send and read LocalTime directly, like H2 and Postgres
> already do.
--
This message was sent by Atlassian Jira
(v10.3.26#10030026)
