-
Notifications
You must be signed in to change notification settings - Fork 104
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
Failure when inspecting reverse OneToOneFields #36
Comments
Thanks for reporting this... have you a more practical example for this constellation?!? |
I don't have another example, but is it very simple scenario: If you have two models, when one (A) of the has a OneToOneField to another (B). Then try to Compare several versions of model B. It will fail on getting values. Very ugly solution (just to make it work) would be to modify |
+1 for this |
@aemdy It seems that you might have found a solution for this problem, do you think you might be able to make a pull request from https://github.com/aemdy/django-reversion-compare/commit/da60d7873bbd8fb212f7f076a68b0b52e297796e? Before doing so it might be a good idea to fix the commit messages and clean up the changes into proper commits but other then that it would be great to get this fixed. I have not tried your code so I'm not 100% it works but please do a PR if it does. |
v0.5.4 release is out. Has this been fixed? |
When I try to compare UserMetadata instances, I get the following error:
It seems that it thinks it is a related manager instead of object.
The text was updated successfully, but these errors were encountered: