Difference between revisions of "Features/Duplicate prevention"
Jump to navigation
Jump to search
| Line 1: | Line 1: | ||
== | == What it is == | ||
Example: | |||
Say you had a management system containing employees. These employees have the following information: They have a CV, current working details, and last workday. If a given employees can be in a few different statuses then each of the fields might not make sense. If an employee is in the process of being hired, then they would not have any current work details or a specific last work day. If the employee were in the process of being fired, then their CV would not matter. This example illustrates how you might want to hide away certain record fields depending on which status the record currently is in. Status level dependencies are used to solve this problem. | |||
* Entity: Check for duplicates | * Entity: Check for duplicates | ||
Revision as of 15:17, 24 August 2023
What it is
Example:
Say you had a management system containing employees. These employees have the following information: They have a CV, current working details, and last workday. If a given employees can be in a few different statuses then each of the fields might not make sense. If an employee is in the process of being hired, then they would not have any current work details or a specific last work day. If the employee were in the process of being fired, then their CV would not matter. This example illustrates how you might want to hide away certain record fields depending on which status the record currently is in. Status level dependencies are used to solve this problem.
- Entity: Check for duplicates
- Field: Is part of a unique key
Note checks realtime when entering data