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 Tue, 10 Jan 2006 15:11:06 GMT
Hi Kathey,

I have clipped to JIRA-499 a fix for these regressions. Thanks for the 
heads-up about the version numbers in the canons. I finessed that issue 
by removing the volatile numbers from the canons. Instead, the metadata 
test now compares version numbers internally and only emits 
diff-triggering output if it detects a discrepancy. Keeping this test in 
sync with the version variables in dnc.properties now involves a couple 
edits to metadata.java rather than updating 10 canons.

I would appreciate it if you could review and commit this patch.


Kathey Marsden (JIRA) wrote:

>    [ 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:
>>    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

View raw message