[
https://issues.apache.org/jira/browse/DERBY-499?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12756512#action_12756512
]
Rick Hillegas commented on DERBY-499:
-------------------------------------
Hi Rami,
The problems with re-enabling the BOOLEAN datatype center on
backward-compatibility concerns. I hope to be able to put some time during the
10.6 cycle into fixing DERBY-887. That's a casting bug which stood in the way
of the first attempt to re-enable BOOLEAN. One way forward on this issue might
be to split the work into smaller increments. For instance, if we just
implemented BOOLEAN for embedded usage, that might reduce the compatibility
issues. I would be happy to give you advice about how to tackle this issue if
you want to help out.
I stopped working on this issue because it was not a high priority for my
company.
> 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
> 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.
