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 2010/07/13 21:05:49 UTC

[jira] Closed: (DERBY-4684) Correct the implicit casting of other types to BOOLEAN

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

Rick Hillegas closed DERBY-4684.
--------------------------------


> Correct the implicit casting of other types to BOOLEAN
> ------------------------------------------------------
>
>                 Key: DERBY-4684
>                 URL: https://issues.apache.org/jira/browse/DERBY-4684
>             Project: Derby
>          Issue Type: Bug
>          Components: SQL
>    Affects Versions: 10.6.1.0
>            Reporter: Rick Hillegas
>            Assignee: Rick Hillegas
>             Fix For: 10.7.0.0
>
>         Attachments: derby-4684-01-ab-implicitCastsToBoolean.diff
>
>
> Via a UNION query, it is possible to implicitly cast non-BOOLEAN types to BOOLEAN today. These implicit casts do not obey the SQL Standard rules defined in part 2, section 6.12 (<cast specification>). Derby should support the Standard rules.
> The following query shows how you can implicitly cast a non-BOOLEAN data type to BOOLEAN today:
> select isindex from sys.sysconglomerates where conglomeratename = 'foo'
> union
> values ( 1 )

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