Changes between Initial Version and Version 1 of Ticket #37317
- Timestamp:
- Sep 2, 2026, 1:30:42 PM (112 minutes ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #37317 – Description
initial v1 1 The `createcachetable` management command used to accept one or more ''table_name'' command-line arguments. That behavior was removed from the [https://docs.djangoproject.com/en/1.8/ref/django-admin/#django-admin-createcachetable documentation] in 1.7 when the command was changed to iterate over all `CACHES` , but the [https://github.com/django/django/blob/5180f82f48b589f93cddc7be7896f654a9aec1ad/django/core/management/commands/createcachetable.py#L47-L50 implementation] is still in place with a "Legacy behavior" comment.1 The `createcachetable` management command used to accept one or more ''table_name'' command-line arguments. That behavior was removed from the [https://docs.djangoproject.com/en/1.8/ref/django-admin/#django-admin-createcachetable documentation] in 1.7 when the command was changed to iterate over all `CACHES` (#15888), but the [https://github.com/django/django/blob/5180f82f48b589f93cddc7be7896f654a9aec1ad/django/core/management/commands/createcachetable.py#L47-L50 implementation] is still in place with a "Legacy behavior" comment. 2 2 3 3 Retaining the undocumented legacy behavior adds maintenance burden (e.g., in implementing features like #36830) and creates potential confusion for users who might try to run `createcachetable` with a `CACHES` alias rather than a table name.