#25320: ManyToManyField.null returns True on master (upcoming 1.9), False on
1.8.
-------------------------------------+-------------------------------------
Reporter: akaariai | Owner: nobody
Type: Bug | Status: new
Component: Database layer | Version: master
(models, ORM) |
Severity: Release blocker | Resolution:
Keywords: | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by tomchristie):
Cheap hack example implementation, if we did want to stick with `null =
False`...
Have a private `_to_many = True` on these cases - then easy to get the
same switching logic as is now used in master.
`if field.null or getattr(field, '_to_many', False)`
I assume there'd be nicer ways to get the right switching behavior, but
just presenting this as a "it doesn't have to be difficult" example.
--
Ticket URL: <https://code.djangoproject.com/ticket/25320#comment:6>
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/066.38b59f21931052ddf39de10b52e2988e%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
