Opened 9 years ago
Last modified 9 years ago
#25320 closed Bug
ManyToManyField.null returns True on 1.8, False on 1.7. — at Initial Version
| Reported by: | Anssi Kääriäinen | Owned by: | nobody |
|---|---|---|---|
| Component: | Database layer (models, ORM) | Version: | dev |
| Severity: | Release blocker | Keywords: | |
| Cc: | tom@… | Triage Stage: | Unreviewed |
| Has patch: | yes | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description
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.
Note:
See TracTickets
for help on using tickets.