[
https://issues.apache.org/jira/browse/METAMODEL-198?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14962114#comment-14962114
]
ASF GitHub Bot commented on METAMODEL-198:
------------------------------------------
Github user ankit2711 commented on the pull request:
https://github.com/apache/metamodel/pull/58#issuecomment-148960339
Modified the fix to be now in DefaultQueryRewriter, added tests which work
for Derby, H2 and HSQL. For SQLLite the timestamp insertions also do not store
the milliseconds so skipped for now. Nothing is done in FormatHelper specific
to Timestamp now.
> 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)
