-
-
Notifications
You must be signed in to change notification settings - Fork 483
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
Inconsistencies with field access regarding m2m fields #1186
Comments
11 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi,
Describe the bug
We've been working with historical records assuming that they can be transparently swapped with underlying instances and used in the same context.
To Reproduce
Expected behavior
I expect the m2m field to work the same as it does within django, resolving the through field connection and returning an object associated with the other side of the connection (not sure if this can be a historical object?)
Environment (please complete the following information):
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: