Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Parameter through on ManyToManyField does not get honoured
See original GitHub issueAs per test tortoise.tests.test_two_databases.TestTwoDatabases.test_two_databases_relation
Issue Analytics
- State:
- Created 5 years ago
- Comments:5 (5 by maintainers)
Top Results From Across the Web
Why use "through" argument for ManyToManyField in Django ...
The reason for creating a Membership model is to add extra data that the default model Django automatically creates wouldn't have by default ......
Read more >QuerySet API reference | Django documentation
Returns a new QuerySet containing objects that do not match the given lookup parameters. The lookup parameters ( **kwargs ) should be in...
Read more >The right way to use a ManyToManyField in Django
To maintain a many-to-many relationship between two tables in a database, the only way is to have a third table which has references...
Read more >Making queries — Django 4.1.4 documentation
Returns a new QuerySet containing objects that do not match the given lookup parameters. The lookup parameters ( **kwargs in the above function...
Read more >Tips for Using Django's ManyToManyField - REVSYS
A primary key doesn't exist until a model instance is saved, so that's why both instances have to exist before they can be...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Well, yes
Is real issue here. I will try to fix it today/tomorrow
Seems alright to me - it takes two model names and concats them with
_UPDATE: Oh, I see what you meant on second one, yea, it doesn’t have default value at all, my bad, will fix it too
Resolved in commit