Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Better Debugging: Pretty SQL Rendering for dry runs in terminal #3096

Open
sungchun12 opened this issue Sep 5, 2024 · 2 comments
Open

Better Debugging: Pretty SQL Rendering for dry runs in terminal #3096

sungchun12 opened this issue Sep 5, 2024 · 2 comments
Labels
Feature Adds new functionality

Comments

@sungchun12
Copy link
Contributor

sungchun12 commented Sep 5, 2024

#2935
#3086 (comment)

The goal is to run a command like this: sqlmesh plan --dry-run-render to view pretty SQL rendering in DAG order including all the DDL/DML/pre statements/post statements.

This prevents the need to context switch to query history and break immersion in the sqlmesh workflow.

image

@sungchun12 sungchun12 added the Feature Adds new functionality label Sep 5, 2024
@giovannipcarvalho
Copy link
Contributor

Related #1254?

@sungchun12
Copy link
Contributor Author

This would also be helpful as debug logs while the sqlmesh run or sqlmesh plan command is running so it's clear where the sqlmesh steps failed as getting a query engine specific error message doesn't immediately tell me where it failed. This will also build clarity when "physical tables are being created" for views which don't have any physical data so people don't get confused in the terminal when they see that progress bar.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Feature Adds new functionality
Projects
None yet
Development

No branches or pull requests

2 participants