#14394: Assigning bad data to an m2m attribute should not clear existing data
-------------------------------------+-------------------------------------
Reporter: carljm | Owner: nobody
Type: Bug | Status: closed
Component: Database layer | Version: master
(models, ORM) |
Severity: Normal | Resolution: fixed
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 1
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Claude Paroz <claude@…>):
In [changeset:"7ce9644d9347455ae6f9bd383788a65e4bcadda3"]:
{{{
#!CommitTicketReference repository=""
revision="7ce9644d9347455ae6f9bd383788a65e4bcadda3"
Added a test to ensure bad assignation to M2M doesn't clear data
Refs #14394.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/14394#comment:14>
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 unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/064.4cb2903b057b2b148dca9eaf8b93ddde%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
