Difference between revisions of "Features/Duplicate prevention"

From TempusServa wiki
Jump to navigation Jump to search
Line 2: Line 2:


Example:
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.
   If you are adding a record to an entity, it would be annoying to later find out that the record already exists. Now you have two records with the same data, but with different DataIDs. To prevent this there should be some part of the data in the record that is impossible to exist in another record. An example of this would be the social security number of a person. If you are adding a record of a person whose SSN already exists in the system, then the person is certainly a duplicate.
 


== How to do ==
* Entity: Check for duplicates
* Entity: Check for duplicates
* Field: Is part of a unique key
* Field: Is part of a unique key


Note checks realtime when entering data
Note checks realtime when entering data

Revision as of 15:27, 24 August 2023

What it is

Example: 

 If you are adding a record to an entity, it would be annoying to later find out that the record already exists. Now you have two records with the same data, but with different DataIDs. To prevent this there should be some part of the data in the record that is impossible to exist in another record. An example of this would be the social security number of a person. If you are adding a record of a person whose SSN already exists in the system, then the person is certainly a duplicate.

How to do

  • Entity: Check for duplicates
  • Field: Is part of a unique key

Note checks realtime when entering data

Retrieved from "https://wiki.tempusserva.dk/index.php?title=Features/Duplicate_prevention&oldid=6671"