db-derby-dev mailing list archives

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

Daniel John Debrunner commented on DERBY-382:

In the new section on error messages, I believe all mentions of severity should be removed.
This is a derby specific implementation detail and is not standard based. The SQLException.getErrorCode()
is intentionally specific to each vendor. Derby should not be encouraging applications to
use this method to affect application flow. Application's making decisions based upon SQLExceptions
 is being addressed in JDBC 4.0.
Maybe the third column of the table could be the effect on the transaction and not a numerical

> 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