[
https://issues.apache.org/jira/browse/METAMODEL-198?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14962512#comment-14962512
]
ASF GitHub Bot commented on METAMODEL-198:
------------------------------------------
GitHub user kaspersorensen opened a pull request:
https://github.com/apache/metamodel/pull/59
METAMODEL-198: Implemented timestamp literal based on JDBC spec
Inspired by #58 I decided to make this PR to show what I had in mind as an
alternative patch which aligns closer to the JDBC spec instead of taking the
literalization of timestamps into MetaModel's codebase.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/kaspersorensen/metamodel
METAMODEL-198/timestamp-jdbc
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/metamodel/pull/59.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #59
----
commit f70eb7f54c0a715314b4315beca99819209857c2
Author: Kasper Sørensen <[email protected]>
Date: 2015-10-18T17:14:12Z
METAMODEL-198: Implemented timestamp literal based on JDBC spec
----
> 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)
