docs: add DuckDB community extension tooling page#494
Open
Anant-mishra1729 wants to merge 1 commit into
Open
Conversation
Closes posit-dev#462 - Add get_started/tooling/duckdb.qmd covering install, output modes, piping to other tools, and the temp table limitation - Add DuckDB entry to tooling overview and installation page - Use verified working syntax (CTE with unnest(range(10))) rather than the broken range(10) t(x) alias form documented in ggsql-duckdb README
This file contains hidden or 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
1 participant
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.
Closes #462
What's included
silent,url,spec,html)Notes
The README in
posit-dev/ggsql-duckdbdocumentsrange(10) t(x)as aworking example but this fails with a parse error on v0.4.1. I've filed
a separate bug for that posit-dev/ggsql-duckdb#11. The examples here use
WITH nums AS (SELECT unnest(range(10)) AS x)which is verified working