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

Ignore some sequence allocation mismatches when checking for compatible updates #1524

Merged
merged 1 commit into from
Jul 18, 2024

Conversation

gefjon
Copy link
Contributor

@gefjon gefjon commented Jul 17, 2024

Description of Changes

When checking for schema compatibility before an update, we erroneously considered sequence allocations to be an incompatible change. This means that any module which contained at least one sequence/autoinc column which had allocated more than 4096 values would be impossible to ever update.

With this change, we permit updates where the proposed sequence allocation is less than the known sequence allocation, and use the larger known sequence allocation as the value. This makes it possible to update modules which contain autoinc columns that have allocated more than 4096 values.

API and ABI breaking changes

N/a.

Expected complexity level and risk

1

Testing

Describe any testing you've done, and any testing you'd like your reviewers to do,
so that you're confident that all the changes work as expected!

  • Published new compatible module on mirror of BitCraft alpha 2; John connected and walked around and stuff and said it looked reasonable.

When checking for schema compatibility before an update,
we erroneously considered sequence allocations to be an incompatible change.
This means that any module which contained at least one sequence/`autoinc` column
which had allocated more than 4096 values would be impossible to ever update.

With this change, we permit updates where the proposed sequence allocation
is less than the known sequence allocation,
and use the larger known sequence allocation as the value.
This makes it possible to update modules
which contain `autoinc` columns that have allocated more than 4096 values.
@gefjon gefjon force-pushed the phoebe/update-merge-sequence-allocated branch from fb83e8f to b641960 Compare July 17, 2024 15:11
@gefjon gefjon changed the title Phoebe/update merge sequence allocated Ignore some sequence allocation mismatches when checking for compatible updates Jul 17, 2024
@gefjon gefjon marked this pull request as ready for review July 17, 2024 15:16
@gefjon gefjon requested review from kazimuth and jdetter July 17, 2024 15:16
Copy link
Collaborator

@jdetter jdetter left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Tested against BitCraft, working. We'll get this deployed ASAP. Thanks Phoebe!

Copy link
Contributor

@kazimuth kazimuth left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍

@gefjon gefjon added this pull request to the merge queue Jul 18, 2024
Merged via the queue into master with commit ee7b096 Jul 18, 2024
9 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants