db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rick Hillegas (JIRA)" <j...@apache.org>
Subject [jira] Closed: (DERBY-499) Expose BOOLEAN datatype to end users
Date Wed, 29 Sep 2010 17:50:36 GMT

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

Rick Hillegas closed DERBY-499.
-------------------------------

    Fix Version/s: 10.7.0.0
       Resolution: Fixed

Closing this issue now that the user documentation is checked in.

> Expose BOOLEAN datatype to end users
> ------------------------------------
>
>                 Key: DERBY-499
>                 URL: https://issues.apache.org/jira/browse/DERBY-499
>             Project: Derby
>          Issue Type: Improvement
>          Components: SQL
>    Affects Versions: 10.1.1.0
>            Reporter: Rick Hillegas
>             Fix For: 10.7.0.0
>
>         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.


Mime
View raw message