-
Notifications
You must be signed in to change notification settings - Fork 20
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
Add usability
column to contracts
table
#1660
base: dev
Are you sure you want to change the base?
Conversation
stores/sql/sqlite/migrations/main/migration_00027_contract_usability.sql
Outdated
Show resolved
Hide resolved
654f588
to
36b6ca4
Compare
36b6ca4
to
7f2d604
Compare
stores/sql/mysql/migrations/main/migration_00027_contract_usability.sql
Outdated
Show resolved
Hide resolved
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.
Looking good but need to make sure the migration is tested. Especially the sqlite migration to make sure we are not dropping anything unexpectedly ^^
stores/sql/sqlite/migrations/main/migration_00027_contract_usability.sql
Show resolved
Hide resolved
stores/sql/sqlite/migrations/main/migration_00027_contract_usability.sql
Show resolved
Hide resolved
tested migrations on SQLite and MySQL, scratch databases though but with an entry in the contracts table, seems OK |
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.
Looking good now but requires fixing the conflict since we merged the directory fix
This PR adds a
usability
column to thecontracts
table. This is the first in a series of PRs that removes the notion of a contract set and replaces it with an indication the contract is good for renewal and thus can be used for uploading and downloading. It's an enum to ensure we can extend it without requiring a migration.This PR essentially introduces an unused field called
usability
. Removingcontract_sets
is slightly more involved than I thought it would be. Mostly because of slabs, buffered slabs and the whole health mechanism. I plan on removing it in 3-4 PRs.