Changes between Initial Version and Version 1 of Ticket #29222, comment 7


Ignore:
Timestamp:
Dec 21, 2025, 1:44:23 AM (4 days ago)
Author:
Simon Charette

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #29222, comment 7

    initial v1  
    77> Avoid using `null` on string-based fields such as `CharField` and `TextField`. The Django convention is to use an empty string, not `NULL`, as the “no data” state for string-based fields.
    88
    9 and things have been working this way on Oracle since their inception I'd be more inclined to wont-fix this ticket and accept it as a unfortunate side effect of `interprets_empty_strings_as_nulls`.
     9and things have been working this way on Oracle since their inception I'd be more inclined to wont-fix this ticket and accept it as a unfortunate side effect of `interprets_empty_strings_as_nulls` than change things for an arguably worst default.
Back to Top