-
Notifications
You must be signed in to change notification settings - Fork 208
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
[Wallet]Add last ran wallet version to wallet database. #5252
Labels
Comments
There should be a different database per network, so no need to include the network |
although I suppose it couldn't hurt |
Yeah should be as per: #5250 |
You can already see this version from the |
SWvheerden
added a commit
that referenced
this issue
Mar 24, 2023
Description --- - Network and client APP_VERSION_NUMBER is now stored when wallet is initialized. - Added FFI function `wallet_get_network_and_version` that returns the `network` and `version` of the client that has last accessed the wallet database. Motivation and Context --- For debugging purposes on the client (e.g. Mobile) How Has This Been Tested? --- manually --------- Co-authored-by: SW van Heerden <swvheerden@gmail.com> Co-authored-by: stringhandler <mikethetike@tari.com>
SWvheerden
added a commit
to SWvheerden/tari
that referenced
this issue
Mar 24, 2023
…023-03-24) ### Features * added FFI function `wallet_get_network_and_version` [tari-project#5252](tari-project#5252) ([tari-project#5263](tari-project#5263)) ([4b09b59](tari-project@4b09b59))
Fixed in #5263 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Add the last ran wallet version to the table
WalletSettingSql
.Add the network the wallet is run on on this as well and check it at startup that it matches.
The version should be retrieved from the FFI without initializing the wallet via
walet_create
It should not run any migration on the database etc. It should just try and retrieve the version+ network. If this is not found, it should return None/Null
The text was updated successfully, but these errors were encountered: