Bigint migration step3 for remaining tables#4591
Merged
jochenehret merged 1 commit intomainfrom Oct 13, 2025
Merged
Conversation
jochenehret
force-pushed
the
bigint_mig_step_3ab_remaining_tables
branch
3 times, most recently
from
d1ec6d9 to
9fd0fc9
Compare
* step 3a and b for remaining tables: jobs, delayed_jobs, app_usage_events, service_usage_events * see also #4406
jochenehret
force-pushed
the
bigint_mig_step_3ab_remaining_tables
branch
from
9fd0fc9 to
705c900
Compare
philippthun
approved these changes
Oct 10, 2025
ari-wg-gitbot
added a commit
to cloudfoundry/capi-release
that referenced
this pull request
Oct 13, 2025
Changes in cloud_controller_ng:
- Bigint migration step3 for remaining tables
PR: cloudfoundry/cloud_controller_ng#4591
Author: Jochen Ehret <jochen.ehret@sap.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
A short explanation of the proposed change:
Bigint migration step 3a and b for remaining tables: jobs, delayed_jobs, app_usage_events, service_usage_events
An explanation of the use cases your change solves
Avoids overflow of "int" typed id columns
Links to any other associated PRs
Bigint Migration for 'events' Table (Step 3) #4406
I have reviewed the contributing guide
I have viewed, signed, and submitted the Contributor License Agreement
I have made this pull request to the
mainbranchI have run all the unit tests using
bundle exec rakeI have run CF Acceptance Tests