db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew McIntyre (JIRA)" <j...@apache.org>
Subject [jira] Updated: (DERBY-499) Expose BOOLEAN datatype to end users
Date Thu, 25 Jan 2007 20:42:49 GMT

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

Andrew McIntyre updated DERBY-499:
----------------------------------

    Fix Version/s:     (was: 11.0.0.0)

Unsetting Fix Version on unassigned issues.

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