Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Fix overuse of ON DELETE CASCADE #520

Open
KavikaPalletenne opened this issue Sep 30, 2024 · 2 comments
Open

Fix overuse of ON DELETE CASCADE #520

KavikaPalletenne opened this issue Sep 30, 2024 · 2 comments
Assignees
@KavikaPalletenne @AlexMIaoPU @fritzrehde
Labels
A: Backend Backend related issues A: Frontend Frontend related issues
Milestone
Backend Rewrite

Comments

@KavikaPalletenne
Copy link
Contributor

We can't always CASCADE the deletes, because we want to keep things even if user accounts are deleted. If user is deleted, we put in a dummy id of -1 for example.
@KavikaPalletenne
Copy link
Contributor Author

This also requires FE and all Postgres JOINs to handle the non-existing user case

@KavikaPalletenne KavikaPalletenne added A: Frontend Frontend related issues A: Backend Backend related issues labels Sep 30, 2024
@KavikaPalletenne KavikaPalletenne added this to the Backend Rewrite milestone Sep 30, 2024
@KavikaPalletenne
Copy link
Contributor Author

Can be delayed until we add in user deletion functionality

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@KavikaPalletenne KavikaPalletenne

@AlexMIaoPU AlexMIaoPU

@fritzrehde fritzrehde

Labels
A: Backend Backend related issues A: Frontend Frontend related issues
Projects
None yet
Milestone
Backend Rewrite
Development

No branches or pull requests
3 participants
@KavikaPalletenne @AlexMIaoPU @fritzrehde