GitHub user DaveBirdsall opened a pull request:

    https://github.com/apache/incubator-trafodion/pull/866

    [TRAFODION-2380] New script to help automate Message Guide updating work

    This new script is designed to help automate development work on the 
Messages Guide. In its initial guise, the script does the following:
    
    1. Compares the text in SqlciErrors.txt with that in the Messages Guide
    2. Produces a report of mismatched messages. For each mismatched message it 
shows:
    a. The message text in each of SqlciErrors.txt and the Messages Guide
    b. Any enums used in the code to refer to the message number
    c. A list of regress tests whose expected files might have examples of the 
message
    d. Optionally, a list of all C++ source files with possible references to 
the message number (this option is very slow unfortunately)
    
    With this information a developer can quickly identify what messages in the 
Message Guide are out-of-date or missing. If the developer decides to change 
the text in SqlciErrors.txt, he/she can also see what regression test expected 
files need to be updated. If option d is specified (--codeRefs), the developer 
will also have a list of files in the code where the message is generated. But 
this option presently takes six or seven hours to run and so is best done 
overnight.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/DaveBirdsall/incubator-trafodion Trafodion2380

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/incubator-trafodion/pull/866.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #866
    
----

----


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Reply via email to