[ http://issues.apache.org/jira/browse/DERBY-499?page=all ]

Rick Hillegas updated DERBY-499:
--------------------------------

    Attachment: bug499_doc.zip

I am attaching bug499_doc.zip, which contains changes to the Tuning and 
Reference guides. This zip file contains:

o bug499_doc.diff - the svn diffs for these doc changes
o ref - a directory containing the html for the Reference guide, including 
these changes

I successfully built the html and pdf versions of these two documents. However, 
I had to increase the vm's memory in order to build the pdf version of the 
Reference guide. I didn't explore how much to increase the memory. I simply set 
the ant options as follows before invoking the build:

  export ANT_OPTS="-Xmx512m"

Here's a summary of the doc changes I made:

TUNING GUIDE

I added boolean to the table of getXXX() and setXXX() methods described in the 
section titled "Use the appropriate getXXX and setXXX methods for the type"

REFERENCE GUIDE

I added a section on boolean to the "Data type" roundup.

I also added a row and column for boolean to the "CAST" page under "Built-in 
functions". I also added to that page a paragraph describing the legal 
conversions to and from boolean.

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

Reply via email to