3 ms·
> unless there's some reason not to. Yes. To note, with GDPR there's now legal reasons to do so regarding user personal data. That can be the moment the devs
by makeitdouble 4y ago
> unless there's some reason not to.
Yes.
To note, with GDPR there's now legal reasons to do so regarding user personal data. That can be the moment the devs realize they actually can't delete the data, because they soft deleted for so long, many relations are now interlocked and the data model needs to be changed to give a starting point to the deletion cascade.
My lesson from that was to at least have one test deleting a mock user that spans the maximum data breadth of the service . We caught a bunch of these loops in test at dev time and that was pretty great.
- JohnBooty 4y agoMy lesson from that was to at least have one test deleting a mock user that spans the maximum data breadth of the service . We caught a bunch of these loops in test at dev time and that was pretty great. Thank you. That is SUPER insightful. If it wasn't too late to edit my initial post I would add this.
- Falkon1313 4y agoGood point. That could be tricky when it crosses the boundaries of schema changes and data migrations.