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] Updated: (DERBY-296) Document error messages in the Derby Reference Manual
Date Fri, 17 Jun 2005 23:45:17 GMT
     [ http://issues.apache.org/jira/browse/DERBY-296?page=all ]

Jeff Levitt updated DERBY-296:

    Attachment: derby296revised.zip

Attached is a patch that removes message 0A001, since it was a typo and we have 0A000 in there
which is the same message.  For the messages that are duplicates, I did not remove them. 
I think (and hopefully someone more familiar with the messages can validate this) that those
are messages where Derby wanted to deviate from the original message string in some places.
 However, I cant tell you exactly how Derby knows when to call one and not the other.  In
any case, they are duplicated in the VTI output, and I think the docs should match that. 
If the messages themselves should change, then maybe we can add on a change to the docs that
corresponds to that change.  But for now, do you think we can commit this and make future
changes to this message list as a baseline?  I think it would be prudent to get this much
larger patch committed and then make proper tweaks if the corresponding code changes later.

> Document error messages in the Derby Reference Manual
> -----------------------------------------------------
>          Key: DERBY-296
>          URL: http://issues.apache.org/jira/browse/DERBY-296
>      Project: Derby
>         Type: Task
>   Components: Documentation
>     Versions:
>  Environment: all
>     Reporter: Jeff Levitt
>     Assignee: Jeff Levitt
>     Priority: Minor
>      Fix For:
>  Attachments: ErrorMessageGenerator.java, derby296revised.zip, results.out, rrefexcept13113.dita
> I've spent some time compiling a list of error messages for Derby, to expand on the error
messages section currently in the Reference Manual.  I am about ready to submit a candidate
patch, and I am opening up a JIRA issue to contain it.

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