[
https://issues.apache.org/jira/browse/OPENJPA-2856?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17314210#comment-17314210
]
ASF subversion and git services commented on OPENJPA-2856:
----------------------------------------------------------
Commit ab8090f5566c68fd3d46600158527de14ce622f2 in openjpa's branch
refs/heads/master from Mark Struberg
[ https://gitbox.apache.org/repos/asf?p=openjpa.git;h=ab8090f ]
OPENJPA-2856 improve MariaDB TIME handling
* java.sql.Time parameters must be on date Jan 1st 1970, otherwise MariaDB
won't find anything in the DB
* from > 10 onwards MariaDB supports up to 6 fractions in TIME as well.
> [MariaDB] improve TIME handling
> -------------------------------
>
> Key: OPENJPA-2856
> URL: https://issues.apache.org/jira/browse/OPENJPA-2856
> Project: OpenJPA
> Issue Type: Bug
> Components: jdbc
> Affects Versions: 3.1.2
> Reporter: Mark Struberg
> Assignee: Mark Struberg
> Priority: Major
> Fix For: 3.1.3
>
>
> It seems that MariaDB > 10 supports fractionDigits also for TIME columns
> (although it doesn't show it in selects by default).
> The other glitch we need to fix is that passing a java.sql.Time parameter
> which got converted from a java.util.Date does not get properly matched
> inside the database if the date part of the time internally is not Jan 1st
> 1970.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
