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

What's the best way to implement dry run? #1191

Open
archiewood opened this issue Jul 24, 2023 · 0 comments
Open

What's the best way to implement dry run? #1191

archiewood opened this issue Jul 24, 2023 · 0 comments
Labels
feature request New issue opened using "Feature request" template

Comments

@archiewood
Copy link
Contributor

archiewood commented Jul 24, 2023

Is your feature request related to a problem? Please describe.

Certain cloud databases (eg BigQuery) allow you to see ahead of time how much data running a query will process. This is helpful as it gives you an idea of how much you will be billed.

Dry run also validates your SQL ahead of time to identify errors.

Context
For example, in the bigquery console, it will give you this information for a valid query

image

And if your query is invalid:

image

For bigquery, you can specify a dry run either with a SQL flag ahead of the statement, or by passing a connection setting.

Other databases seem to have somewhat similar functionality available with EXPLAIN, though I am not familiar with the details

Would this feature make sense to have available for the whole SQLTools extension, or develop specifically for the BigQuery Driver?

@archiewood archiewood added the feature request New issue opened using "Feature request" template label Jul 24, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature request New issue opened using "Feature request" template
Projects
None yet
Development

No branches or pull requests

1 participant