-
Notifications
You must be signed in to change notification settings - Fork 201
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
getting error: "no such column: transaction_inputs.witnesses" #378
Comments
Between major versions the database is not automatically updated unfortunately. What you can do is copy the private keys and recreate the wallets. In tools/import_database.py you can find an example of a very basic automated script to import a bunch of wallets. Make sure you backup the database before you run any scripts, but you already knew that... |
I don't see an import_database.py anywhere in this repo |
I think I can figure this out by looking at the source for clw though |
Here's a quick and dirty script I wrote to migrate my wallets from an old database to a new one:
|
I'm sorry, I saw the tools/import_database.py was only available in the latest version and not in the current branch. But your script seems to do the same... |
I have some wallets I created back in 2021 and I recently updated my laptop with the python 3.11 and bitcoinlib 0.6.14 and now when I do this:
I see some wallet info and then a traceback which seems to indicate that my database probably needs a schema upgrade? Is there an easy safe way to do that?
The text was updated successfully, but these errors were encountered: