From dbdc192ca30b70a9f22c6bc4b3155bbccd01c323 Mon Sep 17 00:00:00 2001 From: David Smith Date: Mon, 25 May 2020 17:05:22 +0100 Subject: Preferred usage of among/while to amongst/whilst. --- docs/howto/writing-migrations.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'docs/howto') diff --git a/docs/howto/writing-migrations.txt b/docs/howto/writing-migrations.txt index ab1a897aa0..00dc0dfadf 100644 --- a/docs/howto/writing-migrations.txt +++ b/docs/howto/writing-migrations.txt @@ -327,7 +327,7 @@ If you change a :class:`~django.db.models.ManyToManyField` to use a ``through`` model, the default migration will delete the existing table and create a new one, losing the existing relations. To avoid this, you can use :class:`.SeparateDatabaseAndState` to rename the existing table to the new -table name whilst telling the migration autodetector that the new model has +table name while telling the migration autodetector that the new model has been created. You can check the existing table name through :djadmin:`sqlmigrate` or :djadmin:`dbshell`. You can check the new table name with the through model's ``_meta.db_table`` property. Your new ``through`` -- cgit v1.3