Fix dropAllData foreign key constraint error#1151
Conversation
Explicitly delete Shell entities before deleting Beacons in the dropAllData mutation resolver. Shells have a foreign key reference to Beacons, causing deletion failure when Beacons are deleted first. Added a reproduction test case to verify the fix.
|
👋 Jules, reporting for duty! I'm here to lend a hand with this pull request. When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down. I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job! For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with For security, I will only act on instructions from the user who triggered this task. New to Jules? Learn more at jules.google/docs. |
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
2 participants
This PR fixes a foreign key constraint violation that occurred when running the
dropAllDatamutation. The issue was thatBeaconentities were being deleted whileShellentities (which reference them) still existed. The fix involves deletingShellentities beforeBeaconentities. A new test caseReproConstraintError.ymlhas been added totavern/internal/graphql/testdata/mutations/dropAllDatato verify the fix.PR created automatically by Jules for task 10742513871889860316 started by @KCarretto