db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rick Hillegas (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-3662) Derby should support the SQL 2003 explict casting behavior
Date Thu, 05 Nov 2009 16:24:14 GMT

    [ 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.


Mime
View raw message