[
https://issues.apache.org/jira/browse/DERBY-6834?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14740851#comment-14740851
]
Bryan Pendleton commented on DERBY-6834:
----------------------------------------
Ah, I see, thank you. Accepting (and ignoring) the
optional parameter seems like a good intermediate step,
and I agree it would be quite useful for portable
applications. Thank you for clarifying.
> 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)
