[ http://issues.apache.org/jira/browse/DERBY-499?page=all ]
Rick Hillegas reassigned DERBY-499:
-----------------------------------
Assignee: (was: Rick Hillegas)
Unassigning myself from this issue. If someone wants to tackle this in the
future, please consult DERBY-1029. In order to implement BOOLEAN, you will need
to:
1) Get the BOOLEAN datatype into the DRDA spec
2) Secure the community's permission for a major release which will let you
change the behavior of implicit and explicit BOOLEAN casts.
> Expose BOOLEAN datatype to end users
> ------------------------------------
>
> Key: DERBY-499
> URL: http://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.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.
-
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
