Good point... Rick, I would also check dblook, to make sure it generates boolean columns. It probably works, but just to make sure...
Satheesh Suresh Thalamati wrote: > Hi Rick , > > you may also want to check if import/export works fine with the > BOOLEAN data type, i u have not already done. > > Thanks > -suresh > > > Daniel John Debrunner (JIRA) wrote: > >> [ >> http://issues.apache.org/jira/browse/DERBY-499?page=comments#action_12361007 >> ] >> Daniel John Debrunner commented on DERBY-499: >> --------------------------------------------- >> >> Committed revision 358163 for patch bug499_rev4.diff. >> >> I think the BOOLEAN type should be added to some of the table driven >> tests like parameterMapping.java and casting.java before this jira >> entry is closed. In looking that the data type conversion routines >> the other day it seems >> that there are some strange conversions to/from BOOLEAN allowed. E.g. >> BOOLEAN to VARCHAR FOR BIT DATA. >> >> I did *not* commit the documentaton changes. >> >> >> >>> 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 >>> >>> 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. >> >> >> > > >
