Skip to content
Browse files

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

  • Loading branch information...
1 parent f0d3dd4 commit 4dd5c8581d89a9f8e1e34e14c682584e562bf8b1 @Naddiseo Naddiseo committed with timgraham
Showing with 6 additions and 4 deletions.
  1. +6 −4 docs/ref/migration-operations.txt
View
10 docs/ref/migration-operations.txt
@@ -241,10 +241,12 @@ ORM and/or python code for.
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
-schema operations available. You should be able to translate the ``orm.Model``
-or ``orm["appname", "Model"]`` references from South directly into
-``apps.get_model("appname", "Model")`` references here and leave most of the
-rest of the code unchanged for data migrations.
+schema operations available. Most of the time, you should be able to translate
+the ``orm.Model`` or ``orm["appname", "Model"]`` references from South directly
+into ``apps.get_model("appname", "Model")`` references here and leave most of
+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
either doing it outside the scope of the Django model system (e.g. triggers)

0 comments on commit 4dd5c85

Please sign in to comment.
Something went wrong with that request. Please try again.