db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bryan Pendleton (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (DERBY-6834) CURRENT_TIME and CURRENT_TIMESTAMP should support optional precision argument
Date Sun, 13 Sep 2015 16:07:45 GMT

     [ https://issues.apache.org/jira/browse/DERBY-6834?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Bryan Pendleton updated DERBY-6834:
-----------------------------------
    Summary: CURRENT_TIME and CURRENT_TIMESTAMP should support optional precision argument
 (was: support for CURRENT_TIMESTAMP(precision) appears to be missing)

Thanks for the clear summary, Rick. I updated the issue
title to try to capture the proposal.

> 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)

Mime
View raw message