Update run_query.md

[ialdg]

Hi.
This modification proposal is intended to make the code more elegant and less demanding on the warehouse. Regards.
IL.

What are you changing in this pull request and why?

Checklist

• Review the Content style guide so my content adheres to these guidelines.
• For docs versioning, review how to version a whole page and version a block of content.
• Add a checklist item for anything that needs to happen before this PR is merged, such as "needs technical review" or "change base branch."

Adding or removing pages (delete if not applicable):

• Add/remove page in website/sidebars.js
• Provide a unique filename for new pages
• Add an entry for deleted pages in website/vercel.json
• Run link testing locally with npm run build to update the links that point to deleted pages

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
docs-getdbt-com	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Apr 10, 2024 11:25am

[mirnawong1]

hey @ialdg , great contribution and suggestion! I've collaborated with my teammate @dbeatty10 and it looks like the run_query logic will only run when execute is true regardless if it is guarded with if execute or not. the query will NOT run twice when execute == False and again when execute == True

this is because the run_query is just a user-friendly interface that uses the statement macro. the macro already contains its own [if execute](https://github.com/dbt-labs/dbt-adapters/blob/7392debf7ff1aa5d58c0fe26eb76ac8ade4fe15b/dbt/include/global_project/macros/etc/statement.sql#L5) logic.

based on this, I'm happy to close this pr out since the run_query logic will only run when execute is true. happy to reopen if you have add'l thoughts, and thank you again for contribution ✨