fix: constraint name collision on rebuild with safer relation operations#1600
Closed
saishreeeee wants to merge 2 commits into
Closed
fix: constraint name collision on rebuild with safer relation operations#1600saishreeeee wants to merge 2 commits into
saishreeeee wants to merge 2 commits into
Conversation
saishreeeee
force-pushed
the
PECOBLR-3498
branch
from
July 22, 2026 04:56
8b36ed5 to
80d8ae2
Compare
saishreeeee
changed the title
saishreeeee
marked this pull request as ready for review
July 22, 2026 08:57
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.
Resolves #1091
Description
Defer primary/foreign keys to an
ALTERon the final relation underuse_safer_relation_operations, so an unnamed key's auto-generated name derives from the target table instead of the staging table and no longer collides on rebuild.Checklist
CHANGELOG.mdand added information about my change to the "dbt-databricks next" section.dbt-databricks-pr-readyproject skill for this PR and addressed its merge-readiness feedback