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

Rethink the --x-full-verification flag usability and implementation #542

Open
glevco opened this issue Mar 15, 2023 · 2 comments
Open

Rethink the --x-full-verification flag usability and implementation #542

glevco opened this issue Mar 15, 2023 · 2 comments

Comments

@glevco
Copy link
Contributor

glevco commented Mar 15, 2023

The --x-full-verification flag may be too slow for practical uses, and we could explore alternative implementations.

This would also remove duplicate code from the code base as discussed in the thread below:

Originally posted by @jansegre in #534 (comment)

@jansegre
Copy link
Member

Yes. I think we should either re-implement it with a different approach or remove it in favor of a separate subcommand to restore a database.

@glevco
Copy link
Contributor Author

glevco commented Oct 17, 2024

or remove it in favor of a separate subcommand to restore a database.

I lean more towards this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Todo
Development

No branches or pull requests

2 participants