[ http://issues.apache.org/jira/browse/DERBY-499?page=comments#action_12362216 ]
Rick Hillegas commented on DERBY-499: ------------------------------------- Hi Kathey: Thanks for finding this discrepancy. I think this is what's going on: I checked in new canons for these tests, which reflect the behavior of these tests with the Derby client under jdk 1.4. However, the old behavior of these tests is still preserved on jdk 1.3 (as documented in the functional spec for this feature). I believe that the appropriate action is to check in vm-specific canons for these tests to handle the 1.3 run. If you think this is urgent, I can pull together a patch for this. Otherwise, I can defer this cleanup to the next patch, which will address your other concerns. > 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
