Briq
/
django-polymorphic
6
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

docs: mention RunPython.noop and reset_polymorphic_ctype()

fix_request_path_info
Diederik van der Boor 2017-01-09 15:33:56 +01:00
parent cf663a0e07
commit c76cc663e0
1 changed files with 14 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

19
docs/migrating.rst
View File

@ -41,10 +41,6 @@ can be included in a single Django migration. For example:
MyModel.objects.filter(polymorphic_ctype__isnull=True).update(polymorphic_ctype=new_ct) MyModel.objects.filter(polymorphic_ctype__isnull=True).update(polymorphic_ctype=new_ct)
def backwards_func(apps, schema_editor):
pass
class Migration(migrations.Migration): class Migration(migrations.Migration):
dependencies = [ dependencies = [
@ -58,8 +54,21 @@ can be included in a single Django migration. For example:
name='polymorphic_ctype', name='polymorphic_ctype',
field=models.ForeignKey(related_name='polymorphic_myapp.mymodel_set+', editable=False, to='contenttypes.ContentType', null=True), field=models.ForeignKey(related_name='polymorphic_myapp.mymodel_set+', editable=False, to='contenttypes.ContentType', null=True),
), ),
migrations.RunPython(forwards_func, backwards_func), migrations.RunPython(forwards_func, migrations.RunPython.noop),
] ]
It's recommended to let ``makemigrations`` create the migration file, It's recommended to let ``makemigrations`` create the migration file,
and include the ``RunPython`` manually before running the migration. and include the ``RunPython`` manually before running the migration.
.. versionadded:: 1.1
When the model is created elsewhere, you can also use
the :func:`polymorphic.utils.reset_polymorphic_ctype` function:
.. code-block:: python
from polymorphic.utils import reset_polymorphic_ctype
from myapp.models import Base, Sub1, Sub2
reset_polymorphic_ctype(Base, Sub1, Sub2)
reset_polymorphic_ctype(Base, Sub1, Sub2, ignore_existing=True)