[
https://issues.apache.org/jira/browse/GEODE-4922?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16422666#comment-16422666
]
Nick Reich commented on GEODE-4922:
-----------------------------------
The issue I reopened this ticket for was determined to be caused by the setup
of the tests: MySQL truncates timestamps to second accuracy be default. To get
the expected result from the test, when using MySQL, the level of precision
must be specified. I am re-resolving this ticket, as GEODE-4947 contains
improvements to these tests and solves the issue found.
> JDBC connector does not handle java.util.Date
> ---------------------------------------------
>
> Key: GEODE-4922
> URL: https://issues.apache.org/jira/browse/GEODE-4922
> Project: Geode
> Issue Type: Bug
> Components: extensions, regions
> Affects Versions: 1.4.0
> Reporter: Darrel Schneider
> Assignee: Darrel Schneider
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.6.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Pdx types can have java.util.Date fields or object fields that contain
> java.util.Date.
> When these are written that java.util.Date may cause a failure from the jdbc
> driver if it does not support java.util.Date. Jdbc drivers must support
> java.sql.Date, java.sql.Time, and java.sql.Timestamp but may not support
> java.util.Date.
> The JDBC connector should convert java.util.Date to one of the java.sql
> interfaces using the data type of the column to determine which one to
> convert it to.
> When reading from jdbc back into geode if the pdx field is java.util.Date
> then we should convert the java.sql.* instance to java.util.Date. It is also
> possible we should do this conversion if the pdx field is of type object.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
