db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Rick Hillegas <Richard.Hille...@Sun.COM>
Subject Re: [jira] Commented: (DERBY-499) Expose BOOLEAN datatype to end users
Date Wed, 21 Dec 2005 15:46:28 GMT
Thanks for committing this patch, Dan. I was planning to tackle 
parameterMapping.java as part of addressing Kathey's additional 
concerns. I'll add some more cases to casting.java also.

Who do you think would like to commit the documentation changes?


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
>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:
>>    Reporter: Rick Hillegas
>>    Assignee: Rick Hillegas
>> Attachments: BooleanFS.html, bug499.diff, bug499_doc.zip, bug499_rev2.diff, bug499_rev3.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

View raw message