Use .pk instead of .id when referring to related object.#110
Merged
jedie merged 1 commit intojedie:masterfrom Jan 4, 2019
peterlisak:bug-id
Merged
Use .pk instead of .id when referring to related object.#110jedie merged 1 commit intojedie:masterfrom peterlisak:bug-id
jedie merged 1 commit intojedie:masterfrom
peterlisak:bug-id
Conversation
Owner
|
That sounds very reasonable. |
Owner
|
@peterlisak it's released as v0.8.6 ;) |
Contributor
Author
|
@jedie Cool, thanks! |
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.
In case of relation to model with primary key which is named differently as
id, it is raising the following error when comparing revisions..pkshould be used.