#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 akaariai):
Sorry, I uploaded the wrong version. Reuploaded to the same place now.
And yes, rename is what I was thinking about.
I would like to add lower level tests for .add/.remove so that we know
they work correctly for possible future changes to m2mfield
(to_field/from_field arguments come to mind here). The Meta: auto_created
hack seems ugly, but maybe it could be acceptable for testing, as that was
pretty easy way to test this. Lets see if some other way to test this
surfaces. if not, maybe those tests could be resurrected...
--
Ticket URL: <https://code.djangoproject.com/ticket/18823#comment:7>
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.
