Changes between Initial Version and Version 1 of Ticket #33647, comment 28


Ignore:
Timestamp:
Dec 9, 2025, 10:39:05 PM (7 days ago)
Author:
Simon Charette

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #33647, comment 28

    initial v1  
    1111We could then make adjusting in a following commit targeting `main` by introducing a `parametrized=False` kwarg in `db_type` with a deprecation period and use that in `bulk_update` and Postgres `bulk_create`.
    1212
    13 FWIW you might also be interested in #14094 and #34887 which respectively added support for unparametrized `varchar` (unlimited length) on Postgres and SQLite and the more recent #24920 which added the same for `DecimalField` (backed by `NUMERIC` which is affected by the same root problem as the one discussed here for `CharField`) on all backends but MySQL. I bringing the `DecimalField` example because on MySQL `DECIMAL` without parameters [https://dbfiddle.uk/aI0yqMQA appears to be] an alias for `DECIMAL(10, 0)` so we likely will have to special case some cases here and there to have `parametrized=False` mean ''the loosest type''.
     13FWIW you might also be interested in #14094 and #34887 which respectively added support for unparametrized `varchar` (unlimited length) on Postgres and SQLite and the more recent #24920 which added the same for `DecimalField` (backed by `NUMERIC` which is affected by the same root problem as the one discussed here for `CharField`) on all backends but MySQL.
     14
     15I'm bringing the `DecimalField` example because on MySQL `DECIMAL` without parameters [https://dbfiddle.uk/aI0yqMQA appears to be] an alias for `DECIMAL(10, 0)` so we likely will have to special case some cases here and there to have `parametrized=False` mean ''the loosest type this backend supports'' on all backends.
Back to Top