You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Mike Matrigali (JIRA)" <ji...@apache.org> on 2011/02/08 21:59:57 UTC
[jira] Updated: (DERBY-4625) TIMESTAMP function doesn't accept
nanoseconds
[ https://issues.apache.org/jira/browse/DERBY-4625?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mike Matrigali updated DERBY-4625:
----------------------------------
Assignee: Mike Matrigali (was: C.S. Nirmal J. Fernando)
temp taking ownership to backport to 10.6 and 10.5.
> 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: Mike Matrigali
> Priority: Minor
> Fix For: 10.7.1.1
>
> Attachments: derby-4625-1.diff, derby_4625-2.diff
>
>
> 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.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira