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-4106) The Reference Gulde claims that the INTEGER function can be applied to dates and times
Date Sun, 08 Nov 2009 16:48:32 GMT

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

Bryan Pendleton updated DERBY-4106:

    Attachment: rrefbuiltinteger.html

I removed the reference to date and time in the attached patch proposal.

I checked the manual pages for SMALLINT and BIGINT and observed that
they were correct, and made INTEGER follow their pattern.

I checked that CastingTest.java in the lang suite already verifies
the behavior of the INTEGER function, so no new tests are needed.

This seems like a straightforward fix to the docs.

> The Reference Gulde claims that the INTEGER function can be applied to dates and times
> --------------------------------------------------------------------------------------
>                 Key: DERBY-4106
>                 URL: https://issues.apache.org/jira/browse/DERBY-4106
>             Project: Derby
>          Issue Type: Bug
>          Components: Documentation
>    Affects Versions:
>         Environment: MS Windows XP Professional Version 2002 Service Pack 2, running
NetBeans IDE 6.5 
>            Reporter: Nelson Rodrigues
>            Assignee: Bryan Pendleton
>         Attachments: docs.diff, rrefbuiltinteger.html
> When Derby Reference Manual, version 10.4, explains the INTEGER function is said that:
>  "The INTEGER function returns an integer representation of a number, character string,
> DATE, or time in the form of an integer constant"
> But when I try to convert a DATE to INTEGER I receive an sqlstate 42846: "Cannot convert
types 'DATE'  to 'INTEGER'."
> This is a sample query where the expected result is the integer number 1: 
> select integer(date(1)) from SYSIBM.SYSDUMMY1

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

View raw message