fix: pivot table composite key can be in any order#536
Merged
Conversation
Codecov Report
@@ Coverage Diff @@
## master #536 +/- ##
=====================================
Coverage 100% 100%
=====================================
Files 46 46
Lines 1843 1845 +2
Branches 261 263 +2
=====================================
+ Hits 1843 1845 +2
Continue to review full report at Codecov.
|
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
2 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.
There should not be restrictions in which order pivot tables composite key fields are.
BelongsToMany#createPivotRecord assumed that relates-to tables key was always first. Other parts of the code used correct order => created issues with store indexes.