[ http://issues.apache.org/jira/browse/DERBY-1566?page=comments#action_12433919 ] Laura Stewart commented on DERBY-1566: --------------------------------------
Thank you Jean. Yes, entering in the variables is much better than typing up 170 new messages :-) I look forward to Andrew's solution post 10.2. For the most part I did use what was there for 10.1. However, in many cases "value" was used instead of databaseName where it seemed obvious to me that it should be changed. There are others like that which I changed as well. But only the obvious ones. I'll make these updates now. How long do you think I should wait for additional comments before submitting a patch? > Document SQLStates in 10.2 > -------------------------- > > Key: DERBY-1566 > URL: http://issues.apache.org/jira/browse/DERBY-1566 > Project: Derby > Issue Type: Improvement > Components: Documentation > Affects Versions: 10.2.1.0 > Reporter: Rick Hillegas > Assigned To: Jean T. Anderson > Fix For: 10.2.1.0 > > Attachments: code-4.diff, derby-1566-1.diff, derby-1566-2.diff, > derby-1566-3.diff, derby-1566-generatorDavidJeanJohnRick.diff, > derby1566_DOCS1.diff, ErrorMessageGenerator.david.diffs, > ErrorMessageGenerator.david.diffs2, ErrorMessageGenerator.david.diffs3, > ErrorMessageGenerator.david.java, ErrorMessageGenerator.java, > ErrorMessageGenerator_davidv3_john.diff, newmsgs-10.2.txt, rrefexcept-2.html, > rrefexcept-3.html, rrefexcept-4.dita, rrefexcept-4.html, > rrefexcept71493.html, rrefexcept71493_DOCS1.html > > > We need to update the Reference Guide to document the current list of > SQLStates. This list goes into > Reference Guide > Derby exception messages and SQL states > SQLState and error message reference > The tool mentioned in DERBY-296 may be useful. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
