fix: translate MySQL error 3730 to IntegrityError #1319
Merged
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.
Summary
Translates MySQL error 3730 ("Cannot drop table referenced by foreign key constraint") to
datajoint.errors.IntegrityErrorinstead of letting it pass through as a rawpymysql.err.OperationalError.Problem
When dropping a schema or table referenced by foreign keys:
This raw error is:
Fix
Add error code 3730 to the existing IntegrityError mapping in
translate_query_error():Result
Users can now catch this with
except dj.errors.IntegrityError.Closes
🤖 Generated with Claude Code