3 ms·
If you need to change history you can just create new events that accomplish your mutation -- and even mark them as a type 'change history' or some such obvious
by hesdeadjim 8y ago
If you need to change history you can just create new events that accomplish your mutation -- and even mark them as a type 'change history' or some such obvious identifier so when you inspect the event stream you know exactly what you are looking at.
- ht85 8y agoTo avoid having to implement the whole logic for any event you'd want to revert, you can have a "cancel" event that points to another event. You'd read the cancel events first and simply skip the events they point to.
- jacques_chester 8y ago> If you need to change history you can just create new events that accomplish your mutation -- and even mark them as a type 'change history' or some such obvious identifier so when you inspect the event stream you know exactly what you are looking at. "Right to be forgotten" isn't the same as "right to be redacted".
- mianos 8y agoI agree, this is 100% normal in accounting, as the earlier thread pointed out. If there is an error you add journal entries to the end to make the adjustment. It is funny that this sort of thing was invented in accounting in 1494.