Update: Handle database relations in case of deleting user #289
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
✅ Deploy Preview for boltfun ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Previously, it was not possible to directly delete a user entry from the Users db table, because there are a lot of tables with relations to the user, & you need to manually delete those entries with relation before deleting the user's entry.
But obviously, this is very tedious, so I've updated the DB schema to include rules for automatic handling of the deletion of the user.
All the entries with a user relation will be automatically deleted when a user is deleted EXCEPT:
Those above will be set the
user_idfield tonull.@johnsBeharry
If you have some different thoughts on the rules, let me know.
NOTE
I haven't migrated these DB updates on the production DB, so the deploy preview won't likely work correctly.