#2750: ManyToManyField ignores 'default' option
---------------------------------------------------+------------------------
Reporter: bangcok_dange...@hotmail.com | Owner: nobody
Status: new | Milestone:
Component: Database layer (models, ORM) | Version:
Resolution: | Keywords:
Stage: Someday/Maybe | Has_patch: 0
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
---------------------------------------------------+------------------------
Comment (by subsume):
+1 in favor of documentation update to reflect the status of default and
null in relation to M2Ms.
With signals and a million other tools its easy to get this default and
I'm not certain that I agree with the meaning or obviousness of 'default'
when it comes to this field.
--
Ticket URL: <http://code.djangoproject.com/ticket/2750#comment:9>
Django <http://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-upda...@googlegroups.com.
To unsubscribe from this group, send email to
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en.
