#2750: ManyToManyField ignores 'default' option
-------------------------------------+-------------------------------------
Reporter: bangcok_dangerus@… | Owner: nobody
Type: Bug | Status: new
Component: Database layer | Version:
(models, ORM) | Resolution:
Severity: Normal | Triage Stage: Accepted
Keywords: | Needs documentation: 0
Has patch: 0 | Patch needs improvement: 1
Needs tests: 0 | UI/UX: 0
Easy pickings: 0 |
-------------------------------------+-------------------------------------
Changes (by jarshwah):
* has_patch: 1 => 0
Comment:
While I don't think `default` makes sense for m2m models, it appears that
forms make use of the default option, so we can't simply check/warn and
document. This will involve some deeper investigation with regards to how
forms use the m2m default. I'll try to look into this a little more.
--
Ticket URL: <https://code.djangoproject.com/ticket/2750#comment:21>
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/086.3d95c76d7a1ca0fc16dc2b4a2c378a9b%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.