Repository navigation
fix: map database scheduling conflicts to HTTP 409 - #10
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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
23P01into stableSHIFT_CONFLICTandLEAVE_CONFLICTAPI errors.DATA_INTEGRITY_VIOLATIONresponse for other data integrity failures.Why
Service-level overlap checks improve error messages but cannot prevent races. PostgreSQL remains the concurrency boundary, so its exclusion-constraint failures must be translated into predictable API responses rather than surfacing as HTTP 500.
Validation
GitHub Actions will run the Gradle suite and PostgreSQL integration tests.