Details
Major
Description
I have been tasked with 'make deduping reversal' on a large database. I expect a bunch of subtasks coming off this but am logging this as the meta-issue.
The only 2 approaches I have in my mind at the moment are
1) turn on logging for the site, address some of the problems with it, ensure there is an api to revert an entire specific transaction, or only as it relates to specific contacts, preferably available from the UI reports/
OR
2) figure out a way (probably outside core) to store information specific to a particular pair of contacts being merged. Write something to reverse engineer it.
The second is basically my backup plan in case #1 is just too big, or unperformant. The advantages of #1 compared to #2 are
- audit data is then available for other purposes too
- it protects better against the unpredicted - e.g if I don't know about data in a particular table being relevant I could miss it in #2 whereas in #1 the data is always stored.
