Fix: disable query validations for dbt models#5305
Merged
georgesittas merged 3 commits intomainfrom Sep 8, 2025
Merged
Conversation
georgesittas
commented
Sep 5, 2025
tobymao
reviewed
Sep 5, 2025
tobymao
reviewed
Sep 5, 2025
d8a11f1 to
db464f3
Compare
georgesittas
commented
Sep 8, 2025
acc8d37 to
9946417
Compare
9946417 to
91a403a
Compare
91a403a to
74ea5e3
Compare
izeigerman
approved these changes
Sep 8, 2025
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.
This PR makes the SQL model definition validation opt-in, via a linter rule. It is enabled by default, but only for native SQLMesh projects. This is done to be more lenient when loading dbt projects, since we shouldn't reject models that have, e.g., duplicate projections– they run fine in dbt.