fix: Ensure not null organization_id on deleted payment_provider_customers #3935
Conversation
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
diegocharles
pushed a commit
that referenced
this pull request
Jul 11, 2025
…omers (#3935) ## Context This PR fixes the migration to add a not null constraint on the `payment_provider_customers` table. The migration task was missing an `unscoped` scope, to take the deleted resources into account in the migration. ## Description To make sure it will not cause any issue when running the migration, a new DB migration is added before the one changing the constraint.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Context
This PR fixes the migration to add a not null constraint on the
payment_provider_customerstable.The migration task was missing an
unscopedscope, to take the deleted resources into account in the migration.Description
To make sure it will not cause any issue when running the migration, a new DB migration is added before the one changing the constraint.