#18823: Clear with a M2M field with a through model
-------------------------------------+-------------------------------------
Reporter: anonymous | Owner: nobody
Type: Bug | Status: new
Component: Database layer | Version: 1.4
(models, ORM) | Resolution:
Severity: Release blocker | Triage Stage: Accepted
Keywords: | Needs documentation: 0
Has patch: 1 | Patch needs improvement: 0
Needs tests: 0 | UI/UX: 0
Easy pickings: 0 |
-------------------------------------+-------------------------------------
Comment (by anonymous):
Thanks for taking the time to look at this. Renaming does make things
clearer.
Seems to me that test_to_field_clear and test_to_field_clear_reverse are
still acceptable tests as they don't depend on auto_created. I couldn't
come up with another way to test add and remove. Maybe if the underlying
private methods were always created and just the public add and remove
methods were skipped for non-auto-created models then we could test those
directly. But I didn't want to propose such a large change just for
testing. I'll think about it a little more though as maybe there is a
better solution that I'm missing.
--
Ticket URL: <https://code.djangoproject.com/ticket/18823#comment:8>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
