Changes between Version 2 and Version 3 of Ticket #34510


Ignore:
Timestamp:
Apr 22, 2023, 8:02:05 PM (14 months ago)
Author:
NeodymiumFerBore
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #34510

    • Property Type BugUncategorized
  • Ticket #34510 – Description

    v2 v3  
    11Hello!
     2
     3I actually don't know if this issue will end being a bug, a new feature or a documentation improvement.
    24
    35The `sqlmigrate` command does not follow `replaces` in squashed migration, with original (squashed) migration files deleted. This ticket is roughly the same than #33583. In #31318, the issue is marked as solved with commit [https://github.com/django/django/commit/d88365708c554efe3c786c3be6da1d9de916360f d883657]. Since then, `MigrationLoader` accepts the argument `replace_migrations`. However, [https://github.com/django/django/blob/d88365708c554efe3c786c3be6da1d9de916360f/django/core/management/commands/sqlmigrate.py#L37 the loader instance here] has this option to `False`. I don't see a command option to set it to `True`.
Back to Top