#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:
Keywords: | Someday/Maybe
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by jarshwah):
https://github.com/django/django/pull/3108
I'm of the opinion that `default` for ManyToManyField doesn't make sense.
The default value of a field is used when a model is saved without a user
value. M2M fields can not have a value when being saved (values must be
added with the RelatedManager), so the default value would always be
applied if implemented.
I think the underlying problem of pre-selecting values in the admin for
m2m form fields is orthogonal to whether or not m2m model fields should
respect the default option.
--
Ticket URL: <https://code.djangoproject.com/ticket/2750#comment:17>
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.126c055c5ac703706b72cbe727e67439%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
