[
https://issues.apache.org/jira/browse/METAMODEL-198?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14961882#comment-14961882
]
ASF GitHub Bot commented on METAMODEL-198:
------------------------------------------
Github user ankit2711 commented on the pull request:
https://github.com/apache/metamodel/pull/58#issuecomment-148913788
The build was failing because some tests were added with the use of the
below constructor
new Timestamp(long milliseconds) and then assertion were applied on the
Timestamp in string. The constructor use with long milliseconds involves
timeszone and hence the assertions failed.
Have tested on Postgres and Oracle when using [TIMESTAMP 'yyyy-mm-dd
hh:mm:ss.nnnnnn'] in the query then the database does the conversion with
respect to the format used in the timestamp column of that DB. The format of
the timestamp column in Oracle had the storage of timestamp value in a format
like this 16-OCT-15 04.33.34.646685000 PM.
> Where clauses on timestamp loses the nanoseconds
> ------------------------------------------------
>
> Key: METAMODEL-198
> URL: https://issues.apache.org/jira/browse/METAMODEL-198
> Project: Apache MetaModel
> Issue Type: Bug
> Reporter: Ankit Kumar
>
> Queries having where clause on timestamp column in databases loses the
> nanoseconds.
> This is happening because the Timestamp values are converted to Date object
> using the new Date(long timeInMilliseconds).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
