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


Ignore:
Timestamp:
Sep 13, 2024, 11:47:52 AM (2 months ago)
Author:
Jae Hyuck Sa

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #35759, comment 7

    initial v1  
    77>
    88> but in the end both `varchar` and `text` [https://www.depesz.com/2010/03/02/charx-vs-varcharx-vs-varchar-vs-text/ are aliases for the internal Postgres] `varlena` type so I don't think the argument stands. There are reason why we'd want to allow `CharField(max_length=None)` on [https://code.djangoproject.com/ticket/14094#comment:5 all backends that allow it] which #14094 does a good job at covering.
     9>
     10> Moreover the addition of this feature could allow us to eventually automatically add a check constraint for `max_length` on SQLite by allowing users to disable it entirely by setting the value to `None`.
    911
    1012Thank you for the detailed explanation! :)
    11 >
    12 > Moreover the addition of this feature could allow us to eventually automatically add a check constraint for `max_length` on SQLite by allowing users to disable it entirely by setting the value to `None`.
     13
Back to Top