This PR implements the migration of the MultiWalletSingleTable management mode as separate Askar stores. For each wallet in the MWST setup, a new database is created in the Askar format.
It also adds a check to ensure that the wallet names passed into the migration script align with the wallet names retrieved from the database to be migrated. If a wallet name is passed in that does not correspond to an existing wallet in the database, an UpgradeError is raised. If a wallet name that corresponds to an existing wallet in the database is not passed into the script to be migrated, a MissingWalletError is raised. If the user wishes to migrate some, but not all, of the wallets in a MWST database, they can bypass the MissingWalletError by setting the --allow-missing-wallet argument as True.
This PR implements the migration of the MultiWalletSingleTable management mode as separate Askar stores. For each wallet in the MWST setup, a new database is created in the Askar format.
It also adds a check to ensure that the wallet names passed into the migration script align with the wallet names retrieved from the database to be migrated. If a wallet name is passed in that does not correspond to an existing wallet in the database, an
UpgradeErroris raised. If a wallet name that corresponds to an existing wallet in the database is not passed into the script to be migrated, aMissingWalletErroris raised. If the user wishes to migrate some, but not all, of the wallets in a MWST database, they can bypass theMissingWalletErrorby setting the--allow-missing-walletargument asTrue.