fix: ignore constraints in dbt seed column types#5535
Merged
Conversation
georgesittas
approved these changes
Oct 13, 2025
fresioAS
pushed a commit
to fresioAS/sqlmesh
that referenced
this pull request
May 31, 2026
Signed-off-by: fresioAS <andreas.fredhoi@three60energy.com>
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
2 participants
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.
This PR adds support for parsing dbt seed column definitions that include constraints.
When a seed's column types config contains constraints (e.g.,
integer not null), SQLMesh now:This prevents errors when dbt projects use constraint syntax in seed column type definitions, even though SQLMesh doesn't support constraints on seeds.