db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Van Couvering (JIRA)" <derby-...@db.apache.org>
Subject [jira] Commented: (DERBY-296) Document error messages in the Derby Reference Manual
Date Sat, 11 Jun 2005 02:57:46 GMT
    [ http://issues.apache.org/jira/browse/DERBY-296?page=comments#action_12313354 ] 

David Van Couvering commented on DERBY-296:

Well, I'm looking at the patch, and while I'm I spend time verifying they are all correct,
I want to ask a couple of meta questions:

- Can you give me a sense of how a user would use this?  All the error messages I have seen
in the log print out the SQLSTATE and the error message.  Are there situations when all you
get is the SQLSTATE?  Or is this for developers so they can write code to perform certain
actions when they get a specific SQLSTATE?

- I know there is an ErrorMessage VTI that prints out all the error messages and SQLSTATEs.
 Would it make more sense just to document to a user how they could use ij to print out these
messages from the VTI?  This way you wouldn't have to continue to maintain this list and try
and make sure it's consistent with reality, which seems like a task meant more for Sisyphus
than anyone else :)

- Alternately, could you write a script that runs the VTI and generates the DITA for you?
 I could probably write one pretty quick if you'd like...  

> 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: derby296withchanges.zip
> 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