...
| Info |
|---|
When adding new error diagnostics, pay attention to the management of ComDiagsArea objects. In the Executor, in particular, these objects are created on demand only. See also SQL Diagnostics Architecture and Design. |
Checking the Consistency of the SQL Message Text and the Trafodion Messages Guide
Unfortunately, in the early days of the Trafodion project, we were not very good at keeping the Messages Guide up-to-date. Some work has been done to bring them back into sync (see for example
| Jira |
|---|
| server | ASF JIRA |
|---|
| serverId | 5aa69414-a9e9-3523-82ec-879b028fb15b |
|---|
| key | TRAFODION-2283 |
|---|
|
). If you feel a calling to improve the Messages Guide, there is a script that can help you. In core/sqf/sql/scripts, the Python script analyzeMessageGuide.py compares the Messages Guide text to that in the code. It flags which messages don't match. It also gives details that are useful for researching the message to bring it back into sync. For example, it will tell you if the message is in the Guide but not in the messages file or vice versa. For messages that are in the messages file, it will tell you what enum file the message is defined in (if any) and tell you what modules reference that message (either by number or by enum). It will also tell you if there are regression tests that have examples of the message.Related articles
| Content by Label |
|---|
| showLabels | false |
|---|
| max | 5 |
|---|
| spaces | TRAFODION |
|---|
| showSpace | false |
|---|
| sort | modified |
|---|
| reverse | true |
|---|
| type | page |
|---|
| cql | label in ("sql","errors") and type = "page" and space = "TRAFODION" |
|---|
| labels | SQL Errors |
|---|
|
...
