[ http://issues.apache.org/jira/browse/DERBY-1566?page=comments#action_12433914 ] Jean T. Anderson commented on DERBY-1566: -----------------------------------------
Thanks for doing this, Laura. I hope the pain of 60+ replacements is preferable to inserting 170 new messages manually. :-) I think it's fine to put '<value>' where you aren't sure. The best opportunity to providing real names is with Andrew's properties approach, which will be post-10.2. And post-10.2 is also the best time to fine tune the grammar, etc. in messages. It looks like the 10.1 variable names were brought forward, so I focused on the 170 new messages and assembled a list below. I guessed a few, so would appreciate it if others would check my suggested replacement. === 01J08 === "Unable to open resultSet type <datatypeName>. ResultSet type <datatypeName> opened." Change '<datatypeName>' to '<resultSetType>' (possible values include TYPE_FORWARD_ONLY and TYPE_SCROLL_INSENSITIVE). === 08001 === "<value> : Error connecting to server <serverName> on port <portNumber> with message <messageText>." "SocketException: '<value>'" "Unable to open stream on socket: '<value>'." Change '<value>' to '<error>'. === 28508 === "User '<authorizationID>' does not have <permissionType> permission on column '<2>' of table '<schemaNamet>'.'<tableName>'." Change '<2>' to '<columnName>' and '<schemaNamet>' to '<schemaName>'. === 28509 === "User '<authorizationID>' does not have <1> permission on column '<2>' of table '<schemaNamet>'.'<tableName>' for grant." Change '<1>' to 'permissionType', '<2>' to '<columnName>', and '<schemaNamet>' to '<schemaName>'. === 2850A, 2850B, 2850C, 2850D, 2850E === Change "schemaNamet" to "schemaName" in all these messages. === 58009 === "SocketException: '<value>'" Change '<value>' to '<error>'. === 58014, 58105, 58106, 58017 === Each message has a parameter that looks like this: 0x<commandName> 0x<objectName> 0x<parameterName> 0x<value> Change all these to <value> unless somebody suggests a good replacement. --The 0x suggests hex codes to me. === XJ091 === "Invalid argument: parameter index <indexName> is not an OUT or INOUT parameter." Change '<indexName>' to '<indexNum>'. In other words, I think the message will look something like this: "parameter index 3 is not an OUT or INOUT parameter". === XJ113 === "Unable to open file <fileName> : <value>" Change '<value>' to '<error>' === XSDAL === "Record handle <0value> unexpectedly points to overflow page." Change '<0value>' to '<value>'. === XSRSC === "Cannot backup the database to <value>, it is a database directory." Change '<value>' to '<directory location>'. > 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
