Support for multiple queries per SQL file #3
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hi @dimitri
I have added support for multiple querier per SQL files as supported by other tools. It does support both the original single query per
.sql
file and multiple queries (each tagged individually).default
The most significant change introduced by this PR is naming of the plan files (and other relevant files). New naming changes from
query_file.ext
toquery_file-query_name.ext
.What are your thoughts on this? I understand you might have some particular idea in mind when going with the only single query per file approach. Would be interested to find out more.
If you are happy to go ahead - I would still have to update Example section of README.md.
Cheers!