Do you think it's worth documenting?
--
Ticket URL: <https://code.djangoproject.com/ticket/24052>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
Comment (by aaugustin):
Here's an interesting variant of this problem.
If you attempt to use a relation that's defined in another app, the
relation doesn't exist unless you include that app in your dependencies.
--
Ticket URL: <https://code.djangoproject.com/ticket/24052#comment:1>
* stage: Unreviewed => Accepted
Old description:
> A common use case for RunPython (known in South as data migrations) is to
> port data from one model to another. When you do this across apps, you
> must add the other app to `dependencies`. Other you get a moderately
> helpful:
> `LookupError: No installed app with label 'people'.`
>
> Do you think it's worth documenting?
New description:
A common use case for RunPython (known in South as data migrations) is to
port data from one model to another. When you do this across apps, you
must add the other app to `dependencies`. Otherwise you get a moderately
helpful:
`LookupError: No installed app with label 'people'.`
Do you think it's worth documenting?
--
Comment:
Definitely. I thought this came up before, but I can't find a ticket or
any docs.
--
Ticket URL: <https://code.djangoproject.com/ticket/24052#comment:2>
Comment (by MarkusH):
This should definitely be covered in the docs. I only think I can recall
to have read somewhere are the few lines I wrote down in my
[https://markusholtermann.eu/#how-do-i-add-a-data-migration Django 1.7:
Database Migrations done right] blog post.
--
Ticket URL: <https://code.djangoproject.com/ticket/24052#comment:3>
Comment (by iambibhas):
I recently faced this when migrating a model which had an FK to a custom
user model. The custom user model was added in the migration 0002 of my
accounts app. I had to manually add `0002_migration_name` to the
dependency list for the migration to work, otherwise it'd just complain
that it can't find the custom user model. The user models migration was
not added to the dependency list automatically. I'll check if I can
reproduce this. This happened during the migration that was reported in
#24037.
--
Ticket URL: <https://code.djangoproject.com/ticket/24052#comment:4>
* has_patch: 0 => 1
--
Ticket URL: <https://code.djangoproject.com/ticket/24052#comment:5>
* needs_better_patch: 0 => 1
--
Ticket URL: <https://code.djangoproject.com/ticket/24052#comment:6>
* status: new => closed
* resolution: => fixed
Comment:
In [changeset:"b089759d6025582f36fbea3c4be3855c50b82462" b089759]:
{{{
#!CommitTicketReference repository=""
revision="b089759d6025582f36fbea3c4be3855c50b82462"
Fixed #24052 -- Doc'd how to write data migrations with models in multiple
apps.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/24052#comment:7>
Comment (by Tim Graham <timograham@…>):
In [changeset:"9bb451aedba9761eb78968183d21a7e27a7c7f1b" 9bb451ae]:
{{{
#!CommitTicketReference repository=""
revision="9bb451aedba9761eb78968183d21a7e27a7c7f1b"
[1.7.x] Fixed #24052 -- Doc'd how to write data migrations with models in
multiple apps.
Backport of b089759d6025582f36fbea3c4be3855c50b82462 from master
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/24052#comment:8>
Comment (by Tim Graham <timograham@…>):
In [changeset:"937c8a5a14c08aa3991a5774dae8db60b611dbac" 937c8a5a]:
{{{
#!CommitTicketReference repository=""
revision="937c8a5a14c08aa3991a5774dae8db60b611dbac"
[1.8.x] Fixed #24052 -- Doc'd how to write data migrations with models in
multiple apps.
Backport of b089759d6025582f36fbea3c4be3855c50b82462 from master
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/24052#comment:9>