p15693087
/
django
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

Fixed #23349 -- Clarified details about RunPython's apps argument.

This commit is contained in:
Richard Eames 2014-08-27 10:37:33 -06:00 committed by Tim Graham
parent f0d3dd4f04
commit 4dd5c8581d
1 changed files with 6 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
docs/ref/migration-operations.txt
View File

@ -241,10 +241,12 @@ ORM and/or python code for.
If you're upgrading from South, this is basically the South pattern as an If you're upgrading from South, this is basically the South pattern as an
operation - one or two methods for forwards and backwards, with an ORM and operation - one or two methods for forwards and backwards, with an ORM and
schema operations available. You should be able to translate the ``orm.Model`` schema operations available. Most of the time, you should be able to translate
or ``orm["appname", "Model"]`` references from South directly into the ``orm.Model`` or ``orm["appname", "Model"]`` references from South directly
``apps.get_model("appname", "Model")`` references here and leave most of the into ``apps.get_model("appname", "Model")`` references here and leave most of
rest of the code unchanged for data migrations. the rest of the code unchanged for data migrations. However, ``apps`` will only
have references to models in the current app unless migrations in other apps
are added to the migration's dependencies.
Much like :class:`RunSQL`, ensure that if you change schema inside here you're Much like :class:`RunSQL`, ensure that if you change schema inside here you're
either doing it outside the scope of the Django model system (e.g. triggers) either doing it outside the scope of the Django model system (e.g. triggers)