feat: add duckdb-quack support and enable it by default#571
Open
fuziontech wants to merge 1 commit into
Open
Conversation
This commit adds support for the duckdb-quack extension, enables it by default in resolve.go, duckgres.example.yaml, README.md, and the integration test harness. It also bundles quack in Dockerfile.worker and resolves pre-existing reflect.Ptr lint issues.
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.
This PR adds support for the duckdb-quack extension (from https://github.com/duckdb/duckdb-quack) and enables it by default. It also fixes deprecated reflect.Ptr lint issues.