Changes between Initial Version and Version 1 of Ticket #35625, comment 1
- Timestamp:
- Jul 22, 2024, 3:11:19 PM (4 months ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #35625, comment 1
initial v1 5 5 I think we should mark this one as a release blocker because `db_default` was added in 5.0 and the latter still receives patches for bugs in new features until 5.1 is released? 6 6 7 I'll try to work on a non-invasive patch that canbe backported and likely create another issue to discuss switching the whole DDL generation machinery to provide `(sql: str, params: tuple)` and let the schema editor decide how it wants to deal with parametrization (use it on Postgres + MySQL) and rely on `quote_value` otherwise through a single `supports_parametrized_ddl` feature flag.7 I'll try to work on a non-invasive patch that disable backend parametrization attempts entirely so it can possibly be backported and likely create another issue to discuss switching the whole DDL generation machinery to provide `(sql: str, params: tuple)` and let the schema editor decide how it wants to deal with parametrization (use it on Postgres + MySQL) and rely on `quote_value` otherwise through a single `supports_parametrized_ddl` feature flag.