Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Date: Sat, 12 Sep 2015 21:52:45 +0000 (UTC)
From: "Bryan Pendleton (JIRA)" <jira@apache.org>
To: derby-dev@db.apache.org
Message-ID: <JIRA.12863085.1441898438000.323086.1442094765896@Atlassian.JIRA>
In-Reply-To: <JIRA.12863085.1441898438000@Atlassian.JIRA>
References: <JIRA.12863085.1441898438000@Atlassian.JIRA>
 <JIRA.12863085.1441898438019@arcas>
Subject: [jira] [Updated] (DERBY-6834) support for
 CURRENT_TIMESTAMP(precision) appears to be missing
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ 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
(v6.3.4#6332)