db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jeff Levitt (JIRA)" <derby-...@db.apache.org>
Subject [jira] Commented: (DERBY-380) Doc Review (CLOSED TO FURTHER COMMENTS): Derby Developer's Guide
Date Fri, 01 Jul 2005 00:30:57 GMT
    [ http://issues.apache.org/jira/browse/DERBY-380?page=comments#action_12314839 ] 

Jeff Levitt commented on DERBY-380:
-----------------------------------

Suresh requested in Derby-377 (too late for that commit):

In preparing for Upgrade section ,  Following step is not required:

1.
Force a checkpoint with the earlier version of Derby. To force a 
checkpoint, connect to the database with the older version of the Derby 
software and issue a shutdown request using the shutdown=true attribute on 
the database connection URL, as shown in the following example: 
/* in a java program */
DriverManager.getConnection("jdbc:derby:sample;shutdown=true");

> Doc Review (CLOSED TO FURTHER COMMENTS): 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 was Tuesday, June 28, noon Pacific time.
> PLEASE DO NOT POST ADDITIONAL COMMENTS TO THIS JIRA ISSUE.  If you have additional comments,
please open a JIRA issue for a fixin in a future release, as there is not enough time to incorporate
additional comments.
> 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