Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Message-ID: <2847468.69361283178893439.JavaMail.jira@thor>
Date: Mon, 30 Aug 2010 10:34:53 -0400 (EDT)
From: "C.S. Nirmal J. Fernando (JIRA)" <jira@apache.org>
To: derby-dev@db.apache.org
Subject: [jira] Assigned: (DERBY-4625) TIMESTAMP function doesn't accept
 nanoseconds
In-Reply-To: <32681535.112341271847531633.JavaMail.jira@thor>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

C.S. Nirmal J. Fernando reassigned DERBY-4625:
----------------------------------------------

    Assignee: C.S. Nirmal J. Fernando

> TIMESTAMP function doesn't accept nanoseconds
> ---------------------------------------------
>
>                 Key: DERBY-4625
>                 URL: https://issues.apache.org/jira/browse/DERBY-4625
>             Project: Derby
>          Issue Type: Bug
>          Components: SQL
>    Affects Versions: 10.5.3.0
>            Reporter: Knut Anders Hatlen
>            Assignee: C.S. Nirmal J. Fernando
>            Priority: Minor
>
> The TIMESTAMP function fails if the string argument specifies the number of nanoseconds. It works if the argument is limited to microsecond resolution.
> ij> values timestamp('2010-04-21 12:00:00.123456');
> 1                         
> --------------------------
> 2010-04-21 12:00:00.123456
> 1 row selected
> ij> values timestamp('2010-04-21 12:00:00.123456789');
> ERROR 22008: '2010-04-21 12:00:00.123456789' is an invalid argument to the timestamp function.
> Since Derby (and JDBC) supports nanosecond resolution, the TIMESTAMP function should also support it.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.