#25320: ManyToManyField.null returns True on 1.8, False on 1.7.
-------------------------------------+-------------------------------------
Reporter: akaariai | Owner: nobody
Type: Bug | Status: new
Component: Database | Version: 1.8
layer (models, ORM) |
Severity: Normal | Keywords:
Triage Stage: | Has patch: 0
Unreviewed |
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 | Easy pickings: 0
UI/UX: 0 |
-------------------------------------+-------------------------------------
According to report on PR
https://github.com/django/django/pull/4241#issuecomment-135492016 we
unintentionally changed the flag's value in 1.8. The null flag for
ManyToManyField isn't that well specified to begin with (does it mean can
the joins generate NULL values (True), or can the returned list be None
(False)?). But I don't see any reason to change the flag's value in 1.8,
so fix for 1.8+ seems appropriate.
--
Ticket URL: <https://code.djangoproject.com/ticket/25320>
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/051.e3202210edd1173bb3031381fbc983d2%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
