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
creating a new SQL script from connection forces preview, which could be expensive #3611
Comments
Worth considering, accidentally opening giant data is a consistent theme! @javierluraschi what do you think? |
Where does the sample query get generated for new SQL documents created through this API? I tried diving in myself but couldn't discover the right place. |
@javierluraschi will you still have some time to tackle this? If not let me know and I'll take a look. |
Thanks @javierluraschi! |
I tried this out on both RStudio Server (Red Hat 7.6) and Desktop (MacOS 10.14), with a few databases, and the SQL preview is getting executed as soon as the file is saved |
@ronblum did you test with the latest (development) versions of |
Thank you! Confirmed on several desktop and server installations. I'm leaving this with the "verifying" tag for now, as a reminder to validate when the updated package is live. |
System details
Steps to reproduce the problem
In the Connections pane, click the SQL button and create a new script.
Describe the problem in detail
A new script is created. After accepting the prompt to save the file, the query is run. The default query is e.g.
Describe the behavior you expected
We should avoid running the query as it could be expensive if a very large table is chosen from the database.
The text was updated successfully, but these errors were encountered: