Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Message-ID: <1647212610.1209479156466.JavaMail.jira@brutus>
Date: Tue, 29 Apr 2008 07:25:56 -0700 (PDT)
From: "Rick Hillegas (JIRA)" <jira@apache.org>
To: derby-dev@db.apache.org
Subject: [jira] Commented: (DERBY-499) Expose BOOLEAN datatype to end users
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Rick Hillegas commented on DERBY-499:
-------------------------------------

Thanks for the interest in this feature, Laurent. The issue is currently unassigned, waiting for someone to pick it up. I would be happy to coach someone through the process.

> Expose BOOLEAN datatype to end users
> ------------------------------------
>
>                 Key: DERBY-499
>                 URL: https://issues.apache.org/jira/browse/DERBY-499
>             Project: Derby
>          Issue Type: New Feature
>          Components: SQL
>    Affects Versions: 10.1.1.0
>            Reporter: Rick Hillegas
>         Attachments: BooleanFS.html, BooleanFS.html, BooleanType.html, BooleanType.html, BooleanType.sxw, BooleanType.sxw, bug499.diff, bug499_doc.zip, bug499_jdk13tests.diff, bug499_jdk13tests_rev2.diff, bug499_rev2.diff, bug499_rev3.diff, bug499_rev4.diff, jdk131BooleanFailures.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.
-
You can reply to this email to add a comment to the issue online.