...
Tables which belong to manual merge process are stored in the dedup DB.
ERD
TABLES
- manual_merge_candidates
column | value | description | ||
|---|---|---|---|---|
| id | UUID | record unique ID | ||
| merge_candidate_id | UUID | mpi.merge_candidates.id | ||
| person_id | UUID | the person which will be merged | ||
| master_person_id | UUID | the person who will stay active | ||
| statusstring | varchar(255) | NEW, PROCESSED | ||
| status_reason | text | automate job's comment | ||
| assignee_id | UUID | user_id, who currently reviews request, for new request it's null | ||
| decisionstring | varchar(255) | null, SPLIT, MERGE, TRASH | ||
| inserted_at | DATETIME | |||
| updated_at | DATETIME | inserted_by | updated_by
- manual_merge_requests
column | value | description |
|---|---|---|
| id | UUID | record unique ID |
| manual_merge_candidate_id | UUID | dedup.manual_merge_candidates.id |
| assignee_id | UUID | user_id, who currently reviews request |
| inserted_at | DATETIME | |
| updated_at | DATETIME | |
| status | string | NEW, SPLIT, MERGE, TRASH, POSTPONE |
| comment | string |
...