Repository navigation
fix(postgres): surface check refusals as actionable validation errors - #262
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
1 participant
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.
PostgreSQL can reject a write after admission when a CHECK constraint or transactional quota trigger fires. Preserve SQLSTATE 23514 as the existing validation error through both ordinary and revision-guarded mutations, including the named constraint and database message, so callers receive actionable HTTP 422 feedback. Uniqueness, foreign-key and transport classifications remain unchanged.
Native PostgreSQL regressions cover named/unnamed violations and HTTP POST/PATCH/PUT refusals with unchanged entity data and revision. A portable classification test covers the conditional HTTP boundary. Patch versions are CLI 0.52.5, PostgreSQL 0.18.1 and Acton 0.50.4; no schema migration or dependency addition is required.
Validation passed: formatting; PostgreSQL cargo check; 108 portable PostgreSQL tests; 1,127 PostgreSQL consumer tests; two focused native database/HTTP regressions; all-target strict clippy; and all 15 required CI checks, including all native PostgreSQL contracts and other backend compatibility gates.