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

Drop constraints on proposal and candidate tables #157

Merged
merged 1 commit into from Jan 31, 2024
Merged

Drop constraints on proposal and candidate tables #157

merged 1 commit into from Jan 31, 2024

Conversation

mzur
Copy link
Member

@mzur mzur commented Jan 31, 2024

The constraints basically disabled any query that tried to delete a job because the cascaded delete was terribly slow without an index. This drops the constraint completely because it was not needed in the first place (proposals/candidates can only be deleted together with their jobs).

This is similar to 5cb27dc

The constraints basically disabled any query that tried to delete
a job because the cascaded delete was terribly slow without an index.
This drops the constraint completely because it was not needed in the
first place (proposals/candidates can only be deleted together with
their jobs).
@mzur mzur merged commit c77e573 into master Jan 31, 2024
2 checks passed
@mzur mzur deleted the patch-1 branch January 31, 2024 10:02
mzur added a commit to biigle/largo that referenced this pull request Jan 31, 2024
The indices are crucial for the efficient processing of foreign
key constraints.

See also: biigle/maia#157
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant