Another bunch of fixes to correctly delete users #918
Merged
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
psrok1
force-pushed
the
fix/deleting-users-2
branch
from
600b7a4 to
3439346
Compare
psrok1
force-pushed
the
fix/deleting-users-2
branch
from
00a1ab9 to
3b79c9c
Compare
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.
Your checklist for this pull request
What is the current behaviour?
User can't be deleted if issued any API key for another user or registered another user. NULL values are already expected in these fields by frontend and backend code, but constraints and cascades were set incorrectly.
What is the new behaviour?
User can be deleted and issued_by and registered_by columns are just NULLed.