We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
The M2M relationship using a custom intermediary object is too confuse. It leads to a weird access to works in a song JSON representation:
{ "works": [ { "work": {}, } ] }
The intermediate object is not a real object, so its name is sometimes hard to understand, e.g. songworklink_set.
songworklink_set
Instead, we should use a real WorkLink object with two FKs.
WorkLink
The text was updated successfully, but these errors were encountered:
No branches or pull requests
The M2M relationship using a custom intermediary object is too confuse. It leads to a weird access to works in a song JSON representation:
The intermediate object is not a real object, so its name is sometimes hard to understand, e.g.
songworklink_set
.Instead, we should use a real
WorkLink
object with two FKs.The text was updated successfully, but these errors were encountered: