-
Notifications
You must be signed in to change notification settings - Fork 217
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
database_schema_version
table stores current database schema version.
#3105
Conversation
187839e
to
ceb5357
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍
f5bbf7c
to
1018cd2
Compare
4781217
to
f7f5e42
Compare
I made the following changes to this PR:
@HeinrichApfelmus do you think this PR is ready to be merged or is there anything else you'd like to add? Thanks. |
database_metadata
table stores current database schema (file format) version.database_schema_version
table stores current database schema version.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
😊
0b9b257
to
bda3702
Compare
bda3702
to
bb41b55
Compare
🎆 |
…e-file-format-to-database
Issue Number
ADP-1135
This PR adds a database table
database_metadata
with 1 row and 1 column in it:version
(from here DV).The idea is that wallet library knows (hardcodes) version of the database file format that it expects to work with (EV), and then:
DV > EV
then its a "database from the future" and no changes should be made to it. Following migrations are aborted.DV < EV
then its a database from the past, and it needs to be migrated (the new mechanism to apply migrations isn't implemented yet)DV = EV
then its all good.