Turned this in my mind since few days, and I faced always to go back at the beginning of my thought… do nothing rather to make a complex and probably broken code.
I do not love that but in this case I would like to fix the issue by a documentation chapter.
- State on the data is erased when you delete the user (actual behavior)
- You want to keep the data for any reason you need, then deactivate the user.
What do you think ?