Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Preserving replacement_open functionality #6449

Merged
merged 7 commits into from
Feb 25, 2023
Merged

Conversation

rjatwal
Copy link
Contributor

@rjatwal rjatwal commented Feb 24, 2023

In MotherDuck's next release, we are transitioning from replacement_open to storage_init. However, we don't want to introduce a full-blown storage extension yet. This PR allows us the storage_init as a config-only replacement hook (preserving the previous functionality...as a stepping stone in our transition).

@@ -146,6 +146,8 @@ struct DBConfigOptions {
bool immediate_transaction_mode = false;
//! The set of unrecognized (other) options
unordered_map<string, Value> unrecognized_options;
//! storage_init extension hook is used only for configuration and does not provide a storage_extension
bool extension_init_is_config_only = false;
Copy link
Collaborator

@Mytherin Mytherin Feb 24, 2023

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Having this be a global option means we cannot use extensions that provide a storage back-end (e.g. SQLite) together with extensions that do not. Perhaps we could instead check if the given storage extension provides the attach and create_transaction_manager functions?

Copy link
Collaborator

@Mytherin Mytherin left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks! LGTM

@Mytherin Mytherin merged commit f59b008 into duckdb:master Feb 25, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants