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) support for CURRENT_TIMESTAMP(precision) appears to be missing
Date Sat, 12 Sep 2015 21:52:45 GMT

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

Bryan Pendleton updated DERBY-6834:
    Attachment: firstTry.diff

I took a stab at this (see attached "firstTry.diff").

It compiles, and even passes a bunch of interactive tests.

But it does not pass the regression suite (e.g., DateTimeTest does not pass)

I'm not quite sure what I did wrong, and the test failures didn't make
it obvious. But maybe somebody else might look at my patch and
see how to improve it.

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

View raw message