Skip to content
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

Open
wants to merge 9 commits into
base: dev
Choose a base branch
from
Open

Conversation

peterjan
Copy link
Member

@peterjan peterjan commented Nov 7, 2024

This PR adds a usability column to the contracts 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. Removing contract_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.

@peterjan peterjan self-assigned this Nov 8, 2024
@peterjan peterjan marked this pull request as ready for review November 8, 2024 11:12
Copy link
Member

@ChrisSchinnerl ChrisSchinnerl left a 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 ^^

@peterjan
Copy link
Member Author

Looking good but need to make sure the migration is tested. Especially the sqlite migration to make sure we are not dropping anything unexpectedly ^^

tested migrations on SQLite and MySQL, scratch databases though but with an entry in the contracts table, seems OK

Copy link
Member

@ChrisSchinnerl ChrisSchinnerl left a 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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: In Review
Development

Successfully merging this pull request may close these issues.

2 participants