Changes between Initial Version and Version 1 of Ticket #36643, comment 2


Ignore:
Timestamp:
Oct 8, 2025, 8:32:05 AM (5 weeks ago)
Author:
Alexandru Chirila

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #36643, comment 2

    initial v1  
    99- When I updated the one instance that did NOT received the squashed migrations before, the `manage.py migrate` command was run automatically
    1010- One of the apps did not have any squashed migrations, so it remained marked as applied and appeared updated (i.e. `shortner` in this case)
    11 - The same app `shortner` also was depending on a another app `charts` that has had squashed migration, and as far as Django is concerned it looked like none of the migrations of applied for `charts` but all migrations were applied to `shortner`. Because the when the migrate script ran it marked all migrations as being unapplied for `charts`.
     11- The same app `shortner` also was depending on a another app `charts` that has had squashed migration, and as far as Django is concerned it looked like none of the migrations were applied for `charts` but all migrations were applied to `shortner`. That's because, when the migrate script ran it marked all migrations as being unapplied for `charts`.
    1212- The consistency check was seeing that migrations for `shortner` were applied before `charts`. Even though both apps were up to date will all the schema changes.
    1313
    1414----
    1515
    16 Beeing in this scenario, I thought that: "Hey no problem, the DB itself is up to date. Django has this 'fake' apply migration utility just to bail you out when you mess up massively as I did."
     16Beeing in this scenario, I thought that: "Hey, no problem, the DB itself is up to date. Django has this 'fake' apply migration utility just to bail you out when you mess up massively as I did."
    1717
    1818Well, apparently I could not be bailed out from this scenario by the "fake apply" migration because of this "consistency check". So I ended up messing around directly into django internal tables (which I would rather always avoid) to fix my issue because the "migrate" command refused to do anything at all.
Back to Top