db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stan Bradbury (JIRA)" <derby-...@db.apache.org>
Subject [jira] Commented: (DERBY-380) Doc Review: Derby Developer's Guide
Date Fri, 24 Jun 2005 23:21:58 GMT
    [ http://issues.apache.org/jira/browse/DERBY-380?page=comments#action_12314437 ] 

Stan Bradbury commented on DERBY-380:
-------------------------------------

Stans review:  %%%%    Developers Guide:  Derby and Standards  %%%%

This section consists of a single table that spans approximately 5 pages in the PDF 
document.  Because the columns in this table were jumbled I used the following HTML document
from the IBM Cloudscape 10 site for this review.  This source URL is:  http://publib.boulder.ibm.com/infocenter/cldscp10/index.jsp?topic=/com.ibm.cloudscape.doc/sqlj151.htm
 - refer to this table for edits
	Reference Manual
	Version 10 
	SC18-9248-00

>> The right column sub items under  'Privilege tables' need to have 'no' placed in
the right-hand column - e.g.: 
 TABLE_PRIVILEGES	       SQL92T		no
 COLUMNS_PRIVILEGES   SQL92T		no
 USAGE_PRIVILEGES 	       SQL92T		no

>> Delete the extra 's' at end of left column sting:
' Compound character string constantss '  << extra 's'

>> We implemented INTERSECT in v 10.1.  Change right column value to 'yes'
  for left column value 'INTERSECT' (sub item of 'Table Operations')


> Doc Review: Derby Developer's Guide
> -----------------------------------
>
>          Key: DERBY-380
>          URL: http://issues.apache.org/jira/browse/DERBY-380
>      Project: Derby
>         Type: Improvement
>   Components: Documentation
>  Environment: all
>     Reporter: Jeff Levitt
>     Priority: Minor
>      Fix For: 10.1.1.0

>
> This issue tracks comments for the Derby Developer's Guide. The deadline for posting
comments isTuesday, June 28, noon Pacific time.
> Some guidelines to follow when posting comments to this issue are:
> - Try to make clear and concise comments about what you want changed whenever possible.
 Provide concrete comments that say "Please change <original> to <modified>" instead
of generic comments like "This section needs to be rewritten."
> - If you're reviewing the HTML Files copy, include the URL for the page in the review
comment. Obtain the URL like this:
>     * highlight the topic in the left frame
>     * right click
>     * choose "Properties"
>     * copy and paste the address in the pop up box.
> - If you're reviewing the PDF copy, in the review comment:
>     * Include the page number for the PDF, and indicate whether the number is the PDF
sheet number or the printed page number.
>     * Include the title of the section that the problem occurs in. If it's in a subsection,
try to include the hierarchy of titles.
> - Please don't review the HTML Book copy -- it'll be time consuming to match up that
copy with the underlying DITA source.

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


Mime
View raw message