Skip to content

Handle ModelSerializer case for relationships to models with custom pk. #4571

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Oct 13, 2016

Conversation

tomchristie
Copy link
Member

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.

@tomchristie tomchristie added this to the 3.5.0 Release milestone Oct 13, 2016
@tomchristie tomchristie changed the title Fix 3674 Handle ModelSerializer case for relationships to models with custom pk. Oct 13, 2016
@tomchristie tomchristie merged commit 8d0a91b into master Oct 13, 2016
@tomchristie tomchristie deleted the fix-3674 branch October 13, 2016 11:43
@tomchristie
Copy link
Member 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