Query check tmp service or location duplicate: Difference between revisions
Jump to navigation
Jump to search
Ttenbergen (talk | contribs) mNo edit summary |
Ttenbergen (talk | contribs) m →Log |
||
Line 21: | Line 21: | ||
== Log == | == Log == | ||
* 2021-09-02 - removed "item" from listing since we don't allow duplicates even if the item is different | |||
* 2021-05-04 - changed query to catch a scenario I had not thought of earlier | * 2021-05-04 - changed query to catch a scenario I had not thought of earlier | ||
* 2021-01-15 - check implemented | * 2021-01-15 - check implemented |
Revision as of 13:43, 2021 September 2
Data Integrity Checks | |
Summary: | Service tmp entry and Boarding_Loc entries must not have duplicate dates and services resp. locations and comments |
Related: | Service tmp entry, Boarding_Loc |
Firmness: | hard check |
Timing: | always |
App: | CCMDB.accdb |
Coding: | query check_tmp_service_or_location_duplicate |
Uses L Problem table: | not relevant for this app |
Status: | implemented |
Implementation Date: | 2021-01-15 |
Backlogged: | No |
This is almost but not quite the same as query check_tmp_2_BL_TR_S_same_tm.
|
|
Log
- 2021-09-02 - removed "item" from listing since we don't allow duplicates even if the item is different
- 2021-05-04 - changed query to catch a scenario I had not thought of earlier
- 2021-01-15 - check implemented
Related articles
Related articles: |
|