db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ramandeep Kaur (JIRA)" <derby-...@db.apache.org>
Subject [jira] Commented: (DERBY-382) Doc Review: Derby Reference Manual
Date Tue, 28 Jun 2005 19:16:00 GMT
    [ http://issues.apache.org/jira/browse/DERBY-382?page=comments#action_12314637 ] 

Ramandeep Kaur commented on DERBY-382:

Reviewed Derby Reference Guide ---> Derby exception messages and SQL states (print page

Have the following comments:

1. Might want to add "This section provides information about ....................................."
in the beginning of this section to be consistent with other user guides.

2. Might want to have space in between severity name and " -"  in the following lines:
Warning Severity-a warning is given but current statement is completed.
Statement Severity-the effects of the current statement, if any, on persistent data are undone.
Transaction Severity-the effects of the current transaction on persistent data are undone;
a rollback is performed.
Session Severity-a rollback is performed and the current session is terminated. This closes
the current connection.
System Severity-the system is shut down. All uncommitted transactions are rolled back.

3. in table "Class Code 42: Syntax Error or Access Rule Violation", 42601 has same msg twice.
42601 in row 3 should have the following message:
42601: In an ALTER TABLE statement, the column '<columnName>' has been specified as
NOT NULL and either the DEFAULT clause was not specified or was specified as DEFAULT NULL.

> Doc Review: Derby Reference Manual
> ----------------------------------
>          Key: DERBY-382
>          URL: http://issues.apache.org/jira/browse/DERBY-382
>      Project: Derby
>         Type: Improvement
>   Components: Documentation
>  Environment: all
>     Reporter: Jeff Levitt
>     Priority: Minor
>      Fix For:

> This issue tracks comments for the Derby Reference Manual. The deadline for posting comments
is Tuesday, 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:
For more information on JIRA, see:

View raw message