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] [Commented] (DERBY-6834) support for CURRENT_TIMESTAMP(precision) appears to be missing
Date Fri, 11 Sep 2015 01:44:45 GMT

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

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

To be explicit, what would be different about your new proposed function,
compared to Derby's existing CURRENT_TIMESTAMP function.

http://db.apache.org/derby/docs/10.11/ref/rrefsqlj15866.html

> support for CURRENT_TIMESTAMP(precision) appears to be missing
> --------------------------------------------------------------
>
>                 Key: DERBY-6834
>                 URL: https://issues.apache.org/jira/browse/DERBY-6834
>             Project: Derby
>          Issue Type: Improvement
>            Reporter: Julian Reschke
>
> 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