Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Message-ID: <714092716.1209998515667.JavaMail.jira@brutus>
Date: Mon, 5 May 2008 07:41:55 -0700 (PDT)
From: "Rick Hillegas (JIRA)" <jira@apache.org>
To: derby-dev@db.apache.org
Subject: [jira] Updated: (DERBY-3662) Derby should support the SQL 2003
 explict casting behavior
In-Reply-To: <1429950039.1209998155693.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


     [ https://issues.apache.org/jira/browse/DERBY-3662?page=3Dcom.atlassia=
n.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. T=
hese include the casting of exact numerics to varchar and the casting of in=
exact numerics to char and varchar. The SQL 2003 rules are defined in part =
2 section 6.12 (<cast specification>). Derby should support the liberal 200=
3 casting behavior. See for instance this user feedback from  Bogdan Calmac=
: http://www.nabble.com/Concatenating-two-numbers-as-a-string-td17036203.ht=
ml#a17036203  (was: The "CAST function" section of the Derby Developer's Gu=
ide says that Derby supports the casts which were legal in SQL 92. There ar=
e a number of casts which are legal in SQL 2003 which Derby does not suppor=
t. These include the casting of exact numerics to varchar and the casting o=
f inexact numerics to char and varchar. The SQL 2003 rules are defined in p=
art 2 section 6.12 (<cast specification>). Derby should support the liberal=
 2003 casting behavior. See for instance this user feedback from  Bogdan Ca=
lmac: http://www.nabble.com/Concatenating-two-numbers-as-a-string-td1703620=
3.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 th=
e 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 behav=
ior. See for instance this user feedback from  Bogdan Calmac: http://www.na=
bble.com/Concatenating-two-numbers-as-a-string-td17036203.html#a17036203

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