feat(errors): register GUARD_STEP_UP_MIN_AGE_ANCHOR condition codes - #1836
Merged
Merged
Conversation
Adds GUARD_STEP_UP_MIN_AGE_ANCHOR_FK_FIELD_CONDITIONS_CONFLICT and GUARD_STEP_UP_MIN_AGE_ANCHOR_CONDITION_FIELD_NOT_FOUND, raised by the anchor_conditions form of the step-up guard introduced in constructive-io/constructive-db#3765.
Contributor
🤖 Devin AI EngineerI'll be helping with this pull request! Here's what you should know: ✅ I will automatically:
Note: I can only respond to comments from users who have write access to this repository. ⚙️ Control Options:
|
|
Review complete. No issues found — approved ✅. This PR updates the database-error inventory registry with two newly encountered PG error codes from
All scanned lenses (api-data, holistic, sweep) found no defects; the entries are consistent with the existing registry structure and the generated Reviewed commit: 1bc15c2 |
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
Registers the two codes raised by the new
anchor_conditionsform of the step-up guard (constructive-io/constructive-db#3765, follow-up noted on constructive-io/constructive-planning#2055):GUARD_STEP_UP_MIN_AGE_ANCHOR_FK_FIELD_CONDITIONS_CONFLICT(403) —min_age_anchorgiven bothfk_colandanchor_conditionsGUARD_STEP_UP_MIN_AGE_ANCHOR_CONDITION_FIELD_NOT_FOUND(404) — an anchor condition references a column the anchor table lacksBoth entries are what
audit-db-errors.pyproduces against currentconstructive-dbmain;registry.generated.tsis regenerated from the inventory (799 → 801).Deliberately not a full inventory regen. A full
audit-db-errors.pyrun also drops the sevenSTORAGE_*lifecycle codes added in ecf19ca — those have no source inconstructive-dbyet (pre-registered ahead of the storage lifecycle SQL) andstorage-lifecycle.test.tsasserts they stay in the inventory. Only the two new entries were merged in so that work is left intact.Link to Devin session: https://app.devin.ai/sessions/161aafecdcac47119f0a61dc759bb3eb
Open in Devin Desktop: https://app.devin.ai/desktop/session/161aafecdcac47119f0a61dc759bb3eb?variant=devin
Requested by: @pyramation