[ http://issues.apache.org/jira/browse/DERBY-499?page=comments#action_12362035 ]
Kathey Marsden commented on DERBY-499: -------------------------------------- Ignore previously deleted comment on this issue. There are two failures in jdk131 that I think might be related to the patch for this issue. Test output is attached as jdk131BooleanFailures.zip. derbyall/derbynetclientmats/derbynetmats.fail:jdbcapi/metadata.java derbyall/derbynetclientmats/derbynetmats.fail:lang/syscat.sql > 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, 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
