db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Knut Anders Hatlen (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-4658) Allow explicit casts of string values to BOOLEAN
Date Thu, 17 Jun 2010 15:03:23 GMT

    [ https://issues.apache.org/jira/browse/DERBY-4658?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12879798#action_12879798
] 

Knut Anders Hatlen commented on DERBY-4658:
-------------------------------------------

Thanks, Rick. I see that CastNode still calls cn.setNullability(true). Weren't the changes
in BooleanConstantNode.init() sufficient to get the nullability correctly initialized?

> Allow explicit casts of string values to BOOLEAN
> ------------------------------------------------
>
>                 Key: DERBY-4658
>                 URL: https://issues.apache.org/jira/browse/DERBY-4658
>             Project: Derby
>          Issue Type: Improvement
>          Components: SQL
>            Reporter: Rick Hillegas
>            Assignee: Rick Hillegas
>         Attachments: derby-4658-01-aa-booleanCasts.diff, derby-4658-01-ab-booleanCasts.diff
>
>
> The SQL Standard allows strings to be explicitly cast to BOOLEAN values. Strings are
the only type (other than BOOLEAN itself) which can be cast to BOOLEAN. As part of our expanding
support for the BOOLEAN datatype, we should allow these casts.
> Casting string types to boolean is defined by part 2, section 6.12 (<cast specification>),
general rule 20:
> a) Trim whitespace off the string
> b) Then apply the rules in section 5.3 (<literal>). This means that the trimmed
string must be 'TRUE', 'FALSE', or 'UNKNOWN', regardless of case.
> c) Otherwise, raise an exception.

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