Changes between Version 1 and Version 3 of Ticket #27044


Ignore:
Timestamp:
Aug 10, 2016, 11:09:15 AM (8 years ago)
Author:
Tim Graham
Comment:

I'm not sure I understand entirely. I think the idea is that if no migrations are applied, then content types shouldn't need to be updated. How can we reproduce the issue to look into it? Run the test suite for your app?

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #27044

    • Property Summary `apps` passed to post_migrate_signal should have access to migrated apps even when no migration has been applied to them → `apps` passed to post_migrate_signal should contain migrated appconfigs even when no migration has been applied to them

  • Ticket #27044 – Description

    v1 v3  
    11Hi,
    22
    3 I noticed that when one runs `migrate` without arguments (implicitly migrating all apps), the `apps` instance passed to `emit_post_migrate_signal` (https://github.com/django/django/blob/1.10/django/core/management/commands/migrate.py#L221 [here]) contains the migrated apps' configurations only in the first run.
     3I noticed that when one runs `migrate` without arguments (implicitly migrating all apps), the `apps` instance passed to `emit_post_migrate_signal` [https://github.com/django/django/blob/1.10/django/core/management/commands/migrate.py#L221 here]) contains the migrated apps' configurations only in the first run.
    44
    55On subsequent runs, the `plan` list ([https://github.com/django/django/blob/1.10/django/core/management/commands/migrate.py#L136 here]) is empty and `post_migrate_apps` is set to `pre_migrate_apps` ([https://github.com/django/django/blob/1.10/django/core/management/commands/migrate.py#L197 here]), i.e. the unmigrated apps.
Back to Top