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

Change build2test id column type to bigint #2494

Merged
merged 1 commit into from
Oct 15, 2024

Conversation

williamjallen
Copy link
Collaborator

Users have reported issues migrating to post-3.5 commits on master, such as in #2448, due to an inconsistency between database schemas between CDash 2 and 3. This PR resolves the issue by changing the type of the build2test id column to an unsigned bigint, in accordance with Laravel tradition. This also avoids potential overflow concerns. I plan to make a series of future PRs to change the rest of the ID columns to unsigned bigints.

@williamjallen williamjallen added this to the v3.6 milestone Oct 9, 2024
@williamjallen williamjallen linked an issue Oct 9, 2024 that may be closed by this pull request
@williamjallen williamjallen force-pushed the build2test-id-migration branch 2 times, most recently from ef910ec to 201e554 Compare October 9, 2024 14:53
@williamjallen williamjallen force-pushed the build2test-id-migration branch from 201e554 to bb88f73 Compare October 9, 2024 18:28
Copy link
Member

@josephsnyder josephsnyder left a comment

Choose a reason for hiding this comment

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

LGTM! No issues on a new install and the logic looks correct

@josephsnyder josephsnyder added this pull request to the merge queue Oct 15, 2024
Merged via the queue into Kitware:master with commit d47542d Oct 15, 2024
6 checks passed
@williamjallen williamjallen deleted the build2test-id-migration branch October 15, 2024 13:24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Database migration failure from cdash:v3.5.1 to cdash:latest
2 participants