modifies DuckDB docs to describe sql literals #1849
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
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.
While it's subtly referenced in the docs and in a few issues, it was not immediately clear to me how to use a customized DuckDB instance as the backing for SQL code blocks. It's not difficult (the
db.sqlmethod provides the functionality already) but I definitely struggled for a bit before hunting down the source of DuckDBClient and seeing how simple it is.This PR explicitly describes how to do this. I documented it on the DuckDB documentation since that's the place that most canonically discusses creating customized DuckDB instances.
See #1846 (comment).