Opened 9 years ago
Last modified 9 years ago
#25320 closed Bug
ManyToManyField.null returns True on master (upcoming 1.9), False on 1.8. — at Version 1
| 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 (last modified by )
According to report on PR https://github.com/django/django/pull/4241#issuecomment-135492016 we unintentionally changed the flag's value in 1.9. 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.9, so fix for the upcoming 1.9 release seems appropriate.
Change History (1)
comment:1 by , 9 years ago
| Description: | modified (diff) |
|---|---|
| Summary: | ManyToManyField.null returns True on 1.8, False on 1.7. → ManyToManyField.null returns True on master (upcoming 1.9), False on 1.8. |
Note:
See TracTickets
for help on using tickets.