Allow overrride extension repo on a per-extension basis via INSTALL syntax #1866
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
carlopi
changed the title
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.
INSTALL h3 FROM community; LOAD h3;Now implies that h3 has to be fetched from the community extension endpoint.
Previous syntax like:
(that defaults to core)
or
LOAD 'https://community-extensions.duckdb.org/v1.1.1/wasm_eh/h3.duckdb_extension.wasm';remains valid.
Note that
INSTALLis still special cased as being lazy, and this still needs solving in mainline duckdb, and might require changes that will be potentially not be fully compatible, but this is intended only for cases already not working.