Skip to content

Conversation

lovelydinosaur
Copy link
Contributor

Closes #3674
Closes #3852

This fix specifically only addresses the issue described by the test cases.
It is possible that there is a related issue for the 'reverse' relationship case that we also need to deal with, but we can't do that unless/until we have a reproducible test case for it.

@lovelydinosaur lovelydinosaur added this to the 3.5.0 Release milestone Oct 13, 2016
@lovelydinosaur lovelydinosaur changed the title Fix 3674 Handle ModelSerializer case for relationships to models with custom pk. Oct 13, 2016
@lovelydinosaur lovelydinosaur merged commit 8d0a91b into master Oct 13, 2016
@lovelydinosaur lovelydinosaur deleted the fix-3674 branch October 13, 2016 11:43
@lovelydinosaur
Copy link
Contributor Author

Also refs #4290

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

upgrading from 3.3.0 to 3.3.1 causes error: FieldDoesNotExist: <Model> has no field named u'id'
1 participant