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.

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

500 error on project deletion #6448

Closed
di opened this issue Aug 15, 2019 · 1 comment · Fixed by #6450
Closed

500 error on project deletion #6448

di opened this issue Aug 15, 2019 · 1 comment · Fixed by #6450
Assignees
Labels

Comments

@di
Copy link
Member

di commented Aug 15, 2019

Currently project deletion results in a 500 error due to #6339.

This is because the UserEvent and ProjectEvent models have a 'not-null' constraint on the project ID, and are not cascaded (deleted) when the project is deleted.

@di di added the bug 🐛 label Aug 15, 2019
@di di pinned this issue Aug 15, 2019
woodruffw added a commit to trail-of-forks/warehouse that referenced this issue Aug 15, 2019
@woodruffw
Copy link
Member

#6450 patches over this by deleting the orphaned events, but a more permanent solution needs to retain those events.

From chat:

We should ultimately key on users.username and projects.normalized_name. In order to key on the latter, it'll need to be changed from a column_property into a real (and unique) column, which will require a migration.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
2 participants