DuckDBClient.sql #1097
Merged
DuckDBClient.sql #1097
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
following @mbostock’s suggestion #1072 (comment)
|
Do we still need this if we have #1098? I prefer using the sql front matter option if possible. |
|
Yes I think so? It would be useful if you wanted to work with an array of objects computed on the client and use them in sql fenced code blocks. It's possible without this, of course. |
|
Ah, and the dynamic source case you mentioned (e.g., driven by input); sql front matter only works with static sources. |
mbostock
approved these changes
Mar 18, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
implement sql fenced code from DuckDBClient.sql(…)
following @mbostock’s suggestion #1072 (comment)
closes #1072