fix: Support ActiveRecord 7.1 composite primary keys #686
Conversation
This file contains 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
BytewaveMLP
force-pushed
the
fix-rails-71-composite-primary-key
branch
from
3df32cc
to
9b1104d
Compare
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.
ActiveRecord 7.1 added first-party support for composite primary keys, which changed the way the
primary_keymethod behaves; specifically, in cases where a model or table has a composite primary key, this will return an array of attributes rather than just one.Given this gem already has support for composite primary keys through the
composite_primary_keysgem, I just extracted out the work done there to support Rails 7.1's approach.Closes #685.