[jira] Commented: (DERBY-499) Expose BOOLEAN datatype to end users

["Satheesh Bandaram (JIRA)" <de...@db.apache.org>]

    [ http://issues.apache.org/jira/browse/DERBY-499?page=comments#action_12359680 ] 

Satheesh Bandaram commented on DERBY-499:
-----------------------------------------

This patch doesn't allow all boolean expressions. Following would fail:

     Select a>b from t
     values myFunc(current date > '1/1/99')

If you look at additiveExpression() function in sqlgrammar.jj, it has a third parameter 'inSelectClause'. This is currently used to prevent sending boolean values to clients, since there is no support for Boolean. (before the patch)

> Expose BOOLEAN datatype to end users
> ------------------------------------
>
>          Key: DERBY-499
>          URL: http://issues.apache.org/jira/browse/DERBY-499
>      Project: Derby
>         Type: New Feature
>   Components: SQL
>     Versions: 10.1.1.0
>     Reporter: Rick Hillegas
>     Assignee: Rick Hillegas
>  Attachments: BooleanFS.html, bug499.diff, bug499_doc.zip
>
> Veaceslav Chicu started an email thread on 8 August 2005 titled "boolean type". He was disappointed that Derby doesn't support the ansi BOOLEAN datatype. On closer inspection, Derby does internally support this type but does not expose this support to end users.
> Derby should let users declare table columns of type BOOLEAN. This should be an indexable datatype.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira