[
https://issues.apache.org/jira/browse/METAMODEL-198?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14961934#comment-14961934
]
ASF GitHub Bot commented on METAMODEL-198:
------------------------------------------
Github user kaspersorensen commented on the pull request:
https://github.com/apache/metamodel/pull/58#issuecomment-148921871
Also a note on testing - if we add it as a scenario in JdbcTestTemplates
then we can immediately verify it with all the automatic tests that can run for
Derby, H2, HSQLDB, SQLite. If it works for those then I always feel a lot more
comforted that we have something with a certain broader applicability.
> 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)
