[ http://issues.apache.org/jira/browse/DERBY-499?page=all ]
Rick Hillegas updated DERBY-499:
--------------------------------
Attachment: bug499.diff
Attached new rev of patch (bug499.diff) addressing initial issues with
BooleanTest raised by Dan: 1) BooleanTest now extends DerbyJUnitTest rather
than LangSuite. 2) Used Integers rather than Shorts to model SMALLINTs in the
assertRow() calls which track casts from BOOLEAN to numeric and string types.
New rev of BooleanTest runs cleanly.
> Expose BOOLEAN datatype to end users
> ------------------------------------
>
> Key: DERBY-499
> URL: http://issues.apache.org/jira/browse/DERBY-499
> Project: Derby
> Type: New Feature
> Components: SQL
> Versions: 10.1.1.0
> Reporter: Rick Hillegas
> Assignee: Rick Hillegas
> Attachments: BooleanFS.html, bug499.diff, bug499_doc.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
