Changes between Initial Version and Version 1 of Ticket #25320


Ignore:
Timestamp:
Aug 28, 2015, 3:13:48 AM (9 years ago)
Author:
Tom Christie
Comment:

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #25320

    • Property 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.

  • Ticket #25320 – Description

    initial v1  
    1 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.
     1According 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.
Back to Top