[
https://issues.apache.org/jira/browse/METAMODEL-198?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14961885#comment-14961885
]
ASF GitHub Bot commented on METAMODEL-198:
------------------------------------------
Github user kaspersorensen commented on the pull request:
https://github.com/apache/metamodel/pull/58#issuecomment-148914106
Yes but I would love to have it solved in as generically possible way as we
can. If the JDBC spec says that JDBC drivers should take into account the
format of ```{ts 'yyyy-mm-dd hh:mm:ss.f . . .'}``` then that is probably the
sanest to go for as the default. I would expect (but need to verify) that then
the Oracle and PostgreSQL drivers can convert that expression to whatever is
needed in the physical query fired from within the driver.
> 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)
