I think you have a good point about being able to add troubleshooting
tips to specific error messages over time. This does add value to this
document over and above what the ErrorMessages VTI can do.
David
Myrna van Lunteren wrote:
On 6/10/05, *David Van Couvering (JIRA)* <[email protected]
<mailto:[email protected]>> wrote:
[
http://issues.apache.org/jira/browse/DERBY-296?page=comments#action_12313354
<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:
[..snip..]
- 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 :)
[..snip..]
My 2c...: It's in the engine javadoc...But I admit it was harder to find
than I thought. In old Cloudscape manuals this was documented...I
couldn't find an obvious spot in the current manuals...(sorry if I was
particularly blind & it's there).
I am wondering whether users are so used to browsing error message
manuals for other databases that they have a hard time using the
ErrorMessage VTI? Plus, you'd need ij...(or issue a separate sql command
at least).
Maybe we can add more value to this document over the VTI by adding
debugging tips and hints where it seems appropriate at some point...?
Myrna
