Move ExtensionHelper into main DuckDB Class #2563
Merged
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
…ing built-in extensions into main library instead of doing this separately for every API
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.
This PR moves the extension helper into the main DuckDB class, which means any extensions that are statically compiled into the system (e.g. through enabling various cmake flags, such as
BUILD_PARQUET_EXTENSION) are loaded on database startup for all APIs. This simplifies the code and fixes #2505.The DBConfig has an extra option
load_extensionsthat can be used to disable this behavior. If the option is set tofalsethe extension load on start-up is not performed.