Bug Fix for unsafe_remove_check_constraint
in certain Rails version
#102
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.
We identified that for certain rails version ( 6.1+, 7.0 ) , when we use symbol for constraint name, migration fails :
the bug is in this code path :
https://github.com/rails/rails/blob/16d8b82d5e2aca4780c5d10b1fe9a90b33a0e84e/activerecord/lib/active_record/connection_adapters/abstract/schema_statements.rb#L1772-L1773
Note: this bug has been fixed in rails 7.1
This PR mainly overriding
unsafe_remove_check_constraint
method and convertsname
arg toname.to_s