#25320: ManyToManyField.null returns True on master (upcoming 1.9), False on
1.8.
-------------------------------------+-------------------------------------
Reporter: akaariai | Owner: nobody
Type: Bug | Status: closed
Component: Database layer | Version: master
(models, ORM) |
Severity: Release blocker | Resolution: fixed
Keywords: | Triage Stage:
| Unreviewed
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Tim Graham <timograham@…>):
* status: new => closed
* resolution: => fixed
Comment:
In [changeset:"064d4b1cb01cbab0461469254a11c918e6b15cbd" 064d4b1]:
{{{
#!CommitTicketReference repository=""
revision="064d4b1cb01cbab0461469254a11c918e6b15cbd"
Fixed #25320 -- Reverted ManyToManyField.null to False for backwards
compatibility.
Thanks Tom Christie for the report and review.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/25320#comment:9>
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.6e167c6bdcab43f2e8325aad74104ad9%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
