[ http://issues.apache.org/jira/browse/DERBY-499?page=comments#action_12362231 ]
Kathey Marsden commented on DERBY-499: -------------------------------------- For metadata.java, you may want to avoid additional canons because it would mean that you would also have to update the bumpversion target. (The output of this test changes with every new version). It would best I think if the difference can be handled programatically in the test. In terms of when this should be addressed, my personal opinion is that it is never good to have test failures for any significant length of time. When do you expect to submit your next patch? > 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
