Duplicate error messages: Difference between revisions
Ttenbergen (talk | contribs) Created page with "{{Bug needing input}} Some error messages in CCMDB.mdb created by CCMDB Data Integrity Checks create more than one error message..." |
Ttenbergen (talk | contribs) No edit summary |
||
| (14 intermediate revisions by 3 users not shown) | |||
| Line 1: | Line 1: | ||
{{Bug | {{Bug}} | ||
Some error messages in [[CCMDB. | Some error messages in [[CCMDB.accdb]] created by [[Data Integrity Checks| CCMDB Data Integrity Checks]] create more than one error message. | ||
These are based on the events used to trigger error messages. | These are based on the events used to trigger error messages. | ||
The reason it shows up repeatedly recently is that we are implementing more "soft" checks. They use the same triggers as "hard" errors, and we would want to make sure we catch those, and they wouldn’t show up repeated because they would likely be fixed after they first show up. | |||
Implementing [[Cross Check Engine]] would take care of this but it's a major change I haven't had time for. [[User:Ttenbergen|Ttenbergen]] 11:22, 2022 April 21 (CDT) | |||
This problem is worse when we use soft-checks, since those will remain for the duration of a record being on the laptop. Example: [[Query s tmp Boarding Loc ER delay reasonable]] or [[Function long LOS()]]. | |||
Latest revision as of 14:37, 7 October 2025
Some error messages in CCMDB.accdb created by CCMDB Data Integrity Checks create more than one error message. These are based on the events used to trigger error messages.
The reason it shows up repeatedly recently is that we are implementing more "soft" checks. They use the same triggers as "hard" errors, and we would want to make sure we catch those, and they wouldn’t show up repeated because they would likely be fixed after they first show up.
Implementing Cross Check Engine would take care of this but it's a major change I haven't had time for. Ttenbergen 11:22, 2022 April 21 (CDT)
This problem is worse when we use soft-checks, since those will remain for the duration of a record being on the laptop. Example: Query s tmp Boarding Loc ER delay reasonable or Function long LOS().