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 "Rick Hillegas (JIRA)" <ji...@apache.org> on 2008/05/05 16:35:55 UTC

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

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
            Reporter: Rick Hillegas


The "CAST function" section of the Derby Developer's Guide 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.
-
You can reply to this email to add a comment to the issue online.


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

Posted by "Rick Hillegas (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/DERBY-3662?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12773962#action_12773962 ] 

Rick Hillegas commented on DERBY-3662:
--------------------------------------

This issue has come up again on the user list: http://old.nabble.com/implicite-datacasting-to26208648.html#a26208648

> 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
>
> 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.
-
You can reply to this email to add a comment to the issue online.


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

Posted by "Kathey Marsden (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/DERBY-3662?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Kathey Marsden updated DERBY-3662:
----------------------------------

    Component/s: SQL

> 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
>
> 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.
-
You can reply to this email to add a comment to the issue online.


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

Posted by "Rick Hillegas (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/DERBY-3662?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Rick Hillegas updated DERBY-3662:
---------------------------------

    Description: 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  (was: The "CAST function" section of the Derby Developer's Guide 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)

> 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
>            Reporter: Rick Hillegas
>
> 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.
-
You can reply to this email to add a comment to the issue online.