[jira] [Commented] (DERBY-6834) CURRENT_TIME and CURRENT_TIMESTAMP should support optional precision argument

["Bryan Pendleton (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/DERBY-6834?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14742636#comment-14742636 ] 

Bryan Pendleton commented on DERBY-6834:
----------------------------------------

I did some more studying of my 'firstTry.diff' patch.

It turns out that DateTimeTest fails, even on a completely clean sandbox.

And when I look in o.a.dT.functionTests.tests.lang._Suite, DateTimeTest isn't
included in that suite.

So maybe DateTimeTest is known to fail.

At any rate, the failures in DateTimeTest certainly weren't caused by my
code change.

So perhaps nothing is basically wrong with my code change, but as Rick observed
there are a number of other additional details to be considered before we would
move ahead with this project.

Still, maybe the diff will be helpful to those who are interested in pursuing a
possible patch for this issue.


> CURRENT_TIME and CURRENT_TIMESTAMP should support optional precision argument
> -----------------------------------------------------------------------------
>
>                 Key: DERBY-6834
>                 URL: https://issues.apache.org/jira/browse/DERBY-6834
>             Project: Derby
>          Issue Type: Improvement
>            Reporter: Julian Reschke
>         Attachments: firstTry.diff
>
>
> See <http://savage.net.au/SQL/sql-92.bnf.html#current%20timestamp%20value%20function>, <http://www.h2database.com/html/functions.html#current_timestamp>, <http://www.postgresql.org/docs/8.2/static/functions-datetime.html#FUNCTIONS-DATETIME-CURRENT>



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)