-
Notifications
You must be signed in to change notification settings - Fork 72
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
Gracefully handle Foreign Key Constraint Errors #4406
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎ 1 Ignored Deployment
|
Passing run #5345 ↗︎
Details:
Review all test suite changes for PR #4406 ↗︎ |
Codecov ReportAttention:
Additional details and impacted files@@ Coverage Diff @@
## main #4406 +/- ##
==========================================
+ Coverage 87.08% 87.10% +0.01%
==========================================
Files 329 329
Lines 20309 20386 +77
Branches 2610 2627 +17
==========================================
+ Hits 17687 17758 +71
- Misses 2160 2163 +3
- Partials 462 465 +3 ☔ View full report in Codecov by Sentry. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nice @ThomasLaPiana , this makes sense and looks good to me! i was able to verify with some basic local testing with fides_env
(see screenshot below).
only thing is whether we'd want a bit of automated test coverage, if that's not too hard to get in place.
Closes https://ethyca.atlassian.net/browse/PROD-1108?focusedCommentId=37809
Description Of Changes
When someone deletes a
dataset
, it throws an error due to foreign key constraints if there is a referencedconnection
The solution is to update our
delete
logic to more intelligently catch and surface errors relate to foreign key constraints instead of blanket labeling everything as the same error.Code Changes
Steps to Confirm
Steps to Reproduce
no longer work in the Jira ticketPre-Merge Checklist
CHANGELOG.md
The new error message: