You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I want the ability to add a linting rule that prevents the application of a plan if it detects any select * in my models whether it knows they can be expanded or not. This is more to solve for enforcing SQL best practice.
config.yaml/config.py: add a config here to the model_defaults.
If it detects a select * print the file path in the terminal output, so I can easily navigate and fix it.
This is helpful because I was scratching my head adding a column to a single model and wondering why a model upstream kept causing breaking changes downstream. It's because select * was downstream in my other models. I wasted precious time and money making SQLMesh backfill more stuff than it needed to for a silly mistake.
cc @VaggelisD given you worked on the most relevant PR recently.
The text was updated successfully, but these errors were encountered:
sungchun12
changed the title
Dynamically replace select * with fully rendered column names if known
Linting rule to PREVENT select * in general
Jan 30, 2025
I want the ability to add a linting rule that prevents the application of a plan if it detects any
select *
in my models whether it knows they can be expanded or not. This is more to solve for enforcing SQL best practice.config.yaml
/config.py
: add a config here to the model_defaults.If it detects a
select *
print the file path in the terminal output, so I can easily navigate and fix it.This is helpful because I was scratching my head adding a column to a single model and wondering why a model upstream kept causing breaking changes downstream. It's because
select *
was downstream in my other models. I wasted precious time and money making SQLMesh backfill more stuff than it needed to for a silly mistake.cc @VaggelisD given you worked on the most relevant PR recently.
The text was updated successfully, but these errors were encountered: