-
Notifications
You must be signed in to change notification settings - Fork 31
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Create Deleted At Column in the database and back fill user data #530
Comments
Hello! Could you assign this issue to me? Thanks in advance! |
Thank you @eleanorreem you have been assigned this issue! Support Chayn's mission? ⭐ Please star this repo to help us find more contributors like you! |
Thank you @eleanorreem you have been assigned this issue! Support Chayn's mission? ⭐ Please star this repo to help us find more contributors like you! |
@srodif accidentally assigned myself. Ignore the bot - you are assigned! |
Hello @eleanorreem! I have created a pull request for this issue. Should I add something else? |
Just to note that I continue to work on this, for the second action item. |
@srodif I didn't see your comment that you were still working on it - apologies! Can you make a separate PR for the migration work? Thank you! |
Overview
When a user requests to be deleted, we soft delete them and hash their personal details. If we want to find a list of dates users were deleted, we can guess when the user was deleted by seeing if the user is set as
user.active
=false and take the date in theupdatedAt
column. However, we would prefer for this data to have its own column. We want to also add a nullable column to the user called "deletedAt" so we can have the date of when the user was deleted for monitoring purposes. We also want to backfill the dataAction Items
uesr.deletedAt
column to the date ofuser.updatedAt
where theuser.active
is set to falseThe text was updated successfully, but these errors were encountered: