Changes between Initial Version and Version 2 of Ticket #27601


Ignore:
Timestamp:
Dec 14, 2016, 7:06:08 AM (8 years ago)
Author:
Tim Graham
Comment:

The new behavior of raising a validation error to alert the developer of a possible misuse seems more expected to me rather than silently coercing any value to it's bool representation. If you believe the old behavior is better, can you provide a use case that demonstrates its merits? I'm not sure if it's worth documenting as that it looks more like a bug fix that a breakage of public API.

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #27601

    • Property Component Uncategorized → Database layer (models, ORM)
    • Property Type Uncategorized → Bug

  • Ticket #27601 – Description

    initial v2  
    1 As of 1.10, `BooleanField` no longer accepts empty string(`""` ) as False value. Was this change intentional? It was not mentioned in [Backwards incompatible changes in 1.10](https://docs.djangoproject.com/en/1.10/releases/1.10/#backwards-incompatible-1-10) section of manual.
     1As of 1.10, `BooleanField` no longer accepts empty string(`""` ) as False value. Was this change intentional? It was not mentioned in [https://docs.djangoproject.com/en/1.10/releases/1.10/#backwards-incompatible-1-10 Backwards incompatible changes in 1.10] section of manual.
    22
    33
Back to Top