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 "Mamta A. Satoor (JIRA)" <ji...@apache.org> on 2012/09/30 04:46:07 UTC

[jira] [Updated] (DERBY-3662) Derby should support the SQL 2003 explict casting behavior

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

Mamta A. Satoor updated DERBY-3662:
-----------------------------------

    Urgency: Normal
     Labels: derby_triage10_10  (was: )
    
> Derby should support the SQL 2003 explict casting behavior
> ----------------------------------------------------------
>
>                 Key: DERBY-3662
>                 URL: https://issues.apache.org/jira/browse/DERBY-3662
>             Project: Derby
>          Issue Type: Improvement
>          Components: SQL
>            Reporter: Rick Hillegas
>              Labels: derby_triage10_10
>
> The "CAST function" section of the Derby Reference manual says that Derby supports the casts which were legal in SQL 92. There are a number of casts which are legal in SQL 2003 which Derby does not support. These include the casting of exact numerics to varchar and the casting of inexact numerics to char and varchar. The SQL 2003 rules are defined in part 2 section 6.12 (<cast specification>). Derby should support the liberal 2003 casting behavior. See for instance this user feedback from  Bogdan Calmac: http://www.nabble.com/Concatenating-two-numbers-as-a-string-td17036203.html#a17036203

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira