entityMap|blocks|key|1qdpr|text|您可以做的另一件事是删除手动创建的表。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|j5s5|随之而来的是，您必须删除该特定的迁移文件。此外，您还必须|g7as|删除django-migrations表中的特定条目|2lhdr|(可能是您的案例中的最后一个)，它与特定的迁移相关。^0|0|0|0^^$0|$]|1|@$2|3|4|5|6|7|8|I|9|@]|A|@]|B|$]]|$2|C|4|D|6|7|8|J|9|@]|A|@]|B|$]]|$2|E|4|F|6|7|8|K|9|@]|A|@]|B|$]]|$2|G|4|H|6|7|8|L|9|@]|A|@]|B|$]]]]

The other thing that you can do is delete the table created manually. 

Along with that, you will have to delete that particular migration file. Also, you will have to delete that particular entry in the django-migrations table(probably the last one in your case) which correlates to that particular migration.

entityMap|blocks|key|8g8ci|text|Alasdair的答案涵盖了基础知识|type|unstyled|depth|inlineStyleRanges|entityRanges|data|er3kj|通过以下方式确定您想要的迁移|9b3fc|使用应用程序名称和迁移名称|4mvr8|但应该指出的是，并不是所有的迁移|a3208|可以|3hg65|被颠倒。如果Django没有反转规则，就会发生这种情况。对于您通过以下方式自动进行迁移的大多数更改|3lpjd|，反转将是可能的。但是，自定义脚本需要同时编写正向和反向代码，如下面的示例所述：|25pse|https://docs.djangoproject.com/en/1.9/ref/migration-operations/|7mbkt|如何进行无操作反转|9a6pn|如果你有一个|cmp3k|操作，那么您可能只想退出迁移，而不是编写逻辑上严格的反转脚本。文档(上面的链接)中对示例的以下快速修改允许这样做，使数据库处于应用迁移后的相同状态，即使在反向迁移之后也是如此。|669dk|#+-*-+coding:+utf-8+-*-
from+__future__+import+unicode_literals

from+django.db+import+migrations,+models

def+forwards_func(apps,+schema_editor):
++++#+We+get+the+model+from+the+versioned+app+registry;
++++#+if+we+directly+import+it,+it'll+be+the+wrong+version
++++Country+=+apps.get_model("myapp",+"Country")
++++db_alias+=+schema_editor.connection.alias
++++Country.objects.using(db_alias).bulk_create([
++++++++Country(name="USA",+code="us"),
++++++++Country(name="France",+code="fr"),
++++])

class+Migration(migrations.Migration):

++++dependencies+=+[]

++++operations+=+[
++++++++migrations.RunPython(forwards_func,+lambda+apps,+schema_editor:+None),
++++]|code-block|syntax|javascript|9f2nr|这适用于Django+1.8、1.9|9js5|更新:写这篇文章的更好的方法是用|5og8r|使用|arlr2|在上面的代码片段中。这两者在功能上是一样的。(评论的功劳)^0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0^^$0|$]|1|@$2|3|4|5|6|7|8|19|9|@]|A|@]|B|$]]|$2|C|4|D|6|7|8|1A|9|@]|A|@]|B|$]]|$2|E|4|F|6|7|8|1B|9|@]|A|@]|B|$]]|$2|G|4|H|6|7|8|1C|9|@]|A|@]|B|$]]|$2|I|4|J|6|7|8|1D|9|@]|A|@]|B|$]]|$2|K|4|L|6|7|8|1E|9|@]|A|@]|B|$]]|$2|M|4|N|6|7|8|1F|9|@]|A|@]|B|$]]|$2|O|4|P|6|7|8|1G|9|@]|A|@]|B|$]]|$2|Q|4|R|6|7|8|1H|9|@]|A|@]|B|$]]|$2|S|4|T|6|7|8|1I|9|@]|A|@]|B|$]]|$2|U|4|V|6|7|8|1J|9|@]|A|@]|B|$]]|$2|W|4|X|6|Y|8|1K|9|@]|A|@]|B|$Z|10]]|$2|11|4|12|6|7|8|1L|9|@]|A|@]|B|$]]|$2|13|4|14|6|7|8|1M|9|@]|A|@]|B|$]]|$2|15|4|16|6|7|8|1N|9|@]|A|@]|B|$]]|$2|17|4|18|6|7|8|1O|9|@]|A|@]|B|$]]]]

The answer by Alasdair covers the basics

<ul>
<li>Identify the migrations you want by <code>./manage.py showmigrations</code></li>
<li><code>migrate</code> using the app name and the migration name</li>
</ul>

But it should be pointed out that not all migrations can be reversed. This happens if Django doesn't have a rule to do the reversal. For most changes that you automatically made migrations by <code>./manage.py makemigrations</code>, the reversal will be possible. However, custom scripts will need to have both a forward and reverse written, as described in the example here:

<a href="https://docs.djangoproject.com/en/1.9/ref/migration-operations/">https://docs.djangoproject.com/en/1.9/ref/migration-operations/</a>

<h2>How to do a no-op reversal</h2>

If you had a <code>RunPython</code> operation, then maybe you just want to back out the migration without writing a logically rigorous reversal script. The following quick hack to the example from the docs (above link) allows this, leaving the database in the same state that it was after the migration was applied, even after reversing it.

<pre class="lang-python prettyprint-override"><code># -*- coding: utf-8 -*-
from __future__ import unicode_literals

from django.db import migrations, models

def forwards_func(apps, schema_editor):
 # We get the model from the versioned app registry;
 # if we directly import it, it'll be the wrong version
 Country = apps.get_model("myapp", "Country")
 db_alias = schema_editor.connection.alias
 Country.objects.using(db_alias).bulk_create([
 Country(name="USA", code="us"),
 Country(name="France", code="fr"),
 ])

class Migration(migrations.Migration):

 dependencies = []

 operations = [
 migrations.RunPython(forwards_func, lambda apps, schema_editor: None),
 ]
</code></pre>

This works for Django 1.8, 1.9

<hr>

Update: A better way of writing this would be to replace <code>lambda apps, schema_editor: None</code> with <code>migrations.RunPython.noop</code> in the snippet above. These are both functionally the same thing. (credit to the comments)

entityMap|blocks|key|a8lka|text|我在1.9.1中做到了这一点(删除上次或最近创建的迁移)：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|9be4f|cm2db|1f40|示例：|4fo61|aoj93|登录到数据库并运行此SQL+(本例中为postgres)|6ruhk|o0dr|然后，我能够创建新的迁移，这些迁移以我刚刚删除的迁移编号(在本例中为11)开始。^0|0|0|0|0|0|0|0^^$0|$]|1|@$2|3|4|5|6|7|8|M|9|@]|A|@]|B|$]]|$2|C|4|-4|6|7|8|N|9|@]|A|@]|B|$]]|$2|D|4|-4|6|7|8|O|9|@]|A|@]|B|$]]|$2|E|4|F|6|7|8|P|9|@]|A|@]|B|$]]|$2|G|4|-4|6|7|8|Q|9|@]|A|@]|B|$]]|$2|H|4|I|6|7|8|R|9|@]|A|@]|B|$]]|$2|J|4|-4|6|7|8|S|9|@]|A|@]|B|$]]|$2|K|4|L|6|7|8|T|9|@]|A|@]|B|$]]]]

I did this in 1.9.1 (to delete the last or latest migration created):

<ol>
<li><code>rm &lt;appname&gt;/migrations/&lt;migration #&gt;*</code>

example: <code>rm myapp/migrations/0011*</code></li>
<li>logged into database and ran this SQL (postgres in this example)

<code>delete from django_migrations where name like '0011%';</code></li>
</ol>

I was then able to create new migrations that started with the migration number that I had just deleted (in this case, 11).

entityMap|blocks|key|2viqo|text|这是我的解决方案，因为上面的解决方案并没有真正涵盖使用案例，当您使用|type|unstyled|depth|inlineStyleRanges|entityRanges|data|dsd0u|..。|esvpr|您可以使用以下命令通过ORM访问表|djd8j|from+django.db.migrations.recorder+import+MigrationRecorder

>>>+MigrationRecorder.Migration.objects.all()
>>>+MigrationRecorder.Migration.objects.latest('id')
Out[5]:+
>>>+MigrationRecorder.Migration.objects.latest('id').delete()
Out[4]:+(1,+{u'migrations.Migration':+1})|code-block|syntax|javascript|1odhd|因此，您可以查询表并删除与您相关的条目。通过这种方式，您可以对其进行详细的修改。使用|7uckq|迁移您还需要处理添加/更改/删除的数据。上面的示例仅显示了如何通过Djang+ORM访问表。^0|0|0|0|0|0^^$0|$]|1|@$2|3|4|5|6|7|8|P|9|@]|A|@]|B|$]]|$2|C|4|D|6|7|8|Q|9|@]|A|@]|B|$]]|$2|E|4|F|6|7|8|R|9|@]|A|@]|B|$]]|$2|G|4|H|6|I|8|S|9|@]|A|@]|B|$J|K]]|$2|L|4|M|6|7|8|T|9|@]|A|@]|B|$]]|$2|N|4|O|6|7|8|U|9|@]|A|@]|B|$]]]]

Here is my solution, since the above solution do not really cover the use-case, when you use <code>RunPython</code>.

You can access the table via the ORM with

<pre><code>from django.db.migrations.recorder import MigrationRecorder

&gt;&gt;&gt; MigrationRecorder.Migration.objects.all()
&gt;&gt;&gt; MigrationRecorder.Migration.objects.latest('id')
Out[5]: &lt;Migration: Migration 0050_auto_20170603_1814 for model&gt;
&gt;&gt;&gt; MigrationRecorder.Migration.objects.latest('id').delete()
Out[4]: (1, {u'migrations.Migration': 1})
</code></pre>

So you can query the tables and delete those entries that are relevant for you. This way you can modify in detail. With <code>RynPython</code> migrations you also need to take care of the data that was added/changed/removed. The above example only displays, how you access the table via Djang ORM.

entityMap|blocks|key|32ava|text|这个答案适用于类似的情况。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|d83eg|如果Alasdair的最高答案没有帮助|a44ts|..。(例如，如果不需要的迁移很快就会在每次新迁移时再次创建，或者如果它处于无法恢复的较大迁移中，或者表已被手动删除。)|tn2n|...delete迁移，而不创建新的迁移？|nkcs|7keir|TL;DR|5qej6|：您可以删除一些上次恢复(混淆)的迁移，然后创建一个新的迁移|9c6h2|修复模型后|hkq8|..。您还可以|ckefk|使用其他方法|fpura|要配置它，请执行以下操作|3g4bq|不创建表|ejg2j|通过迁移命令。|94csf|必须创建最后一个迁移，使其与当前模型匹配|9vjud|..。|c8ss7|案例|66ika|为什么任何人都不想为必须存在的模型创建表：|4k2a7|A)|cruod|这样的表不应存在于任何计算机上的任何数据库中，也不应存在于任何条件下|8idc1|当：|bpdi1|它是仅为其他模型的模型继承而创建的基础模型。|46q74|解决方案：|c5sne|设置|dmphs|B)|17dai|这个表很少创建，或者是通过其他方式创建的，或者是以一种特殊的方式手动创建的。|a0mq3|90rrf|使用|3b90s|aqnem|迁移是创建的，但从未使用过，只在测试中使用。迁移文件很重要，否则数据库测试无法从可重现的初始状态开始运行。|6uulv|C)|4ebd|该表仅在某些机器上使用(例如，在开发中)。|bl107|8k3sd|将模型移动到添加到已安装的新应用程序中|f04pn|_|8pmh6|应用程序仅在特殊条件下或使用条件|4baqo|67iim|D)|ad237|该项目在中使用了多个数据库|c8ne5|2fgl6|写一个|12a2d|数据库路由器|29kbh|使用方法|9k91d|以便区分应该在何处创建表的数据库以及在何处不应该创建表的数据库。|6696m|迁移在所有情况下都是使用Django+1.9%2B创建的A)、B)、C)、D)+(并且仅在使用Django+1.8的情况下B、C、D)，但仅在适当的情况下才应用于数据库，或者如果需要的话，可能从不应用于数据库。从Django+1.8开始，必须进行迁移才能运行测试。迁移记录了完整的相关当前状态，即使是在Django+1.9%2B中使用managed=False的模型，也可以在托管/非托管模型之间创建ForeignKey，或者可以在以后创建模型managed=True。(这个问题在Django+1.8的时候已经写好了。这里的所有内容都应该适用于1.8到当前2.2之间的版本。)|efs2u|如果最后一次迁移不容易恢复，则可以谨慎地(在数据库备份之后)执行|9dd14|伪还原|77dhs|2jgef|，手动删除该表。|8pp49|如有必要，可从固定模型创建固定迁移，并在不更改数据库结构的情况下应用该迁移|gc68^0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0^^$0|$]|1|@$2|3|4|5|6|7|8|2U|9|@]|A|@]|B|$]]|$2|C|4|D|6|7|8|2V|9|@]|A|@]|B|$]]|$2|E|4|F|6|7|8|2W|9|@]|A|@]|B|$]]|$2|G|4|H|6|7|8|2X|9|@]|A|@]|B|$]]|$2|I|4|-4|6|7|8|2Y|9|@]|A|@]|B|$]]|$2|J|4|K|6|7|8|2Z|9|@]|A|@]|B|$]]|$2|L|4|M|6|7|8|30|9|@]|A|@]|B|$]]|$2|N|4|O|6|7|8|31|9|@]|A|@]|B|$]]|$2|P|4|Q|6|7|8|32|9|@]|A|@]|B|$]]|$2|R|4|S|6|7|8|33|9|@]|A|@]|B|$]]|$2|T|4|U|6|7|8|34|9|@]|A|@]|B|$]]|$2|V|4|W|6|7|8|35|9|@]|A|@]|B|$]]|$2|X|4|Y|6|7|8|36|9|@]|A|@]|B|$]]|$2|Z|4|10|6|7|8|37|9|@]|A|@]|B|$]]|$2|11|4|12|6|7|8|38|9|@]|A|@]|B|$]]|$2|13|4|14|6|7|8|39|9|@]|A|@]|B|$]]|$2|15|4|16|6|7|8|3A|9|@]|A|@]|B|$]]|$2|17|4|18|6|7|8|3B|9|@]|A|@]|B|$]]|$2|19|4|1A|6|7|8|3C|9|@]|A|@]|B|$]]|$2|1B|4|1C|6|7|8|3D|9|@]|A|@]|B|$]]|$2|1D|4|1E|6|7|8|3E|9|@]|A|@]|B|$]]|$2|1F|4|1G|6|7|8|3F|9|@]|A|@]|B|$]]|$2|1H|4|1I|6|7|8|3G|9|@]|A|@]|B|$]]|$2|1J|4|1K|6|7|8|3H|9|@]|A|@]|B|$]]|$2|1L|4|1M|6|7|8|3I|9|@]|A|@]|B|$]]|$2|1N|4|1G|6|7|8|3J|9|@]|A|@]|B|$]]|$2|1O|4|1P|6|7|8|3K|9|@]|A|@]|B|$]]|$2|1Q|4|-4|6|7|8|3L|9|@]|A|@]|B|$]]|$2|1R|4|1S|6|7|8|3M|9|@]|A|@]|B|$]]|$2|1T|4|1U|6|7|8|3N|9|@]|A|@]|B|$]]|$2|1V|4|1W|6|7|8|3O|9|@]|A|@]|B|$]]|$2|1X|4|1G|6|7|8|3P|9|@]|A|@]|B|$]]|$2|1Y|4|1Z|6|7|8|3Q|9|@]|A|@]|B|$]]|$2|20|4|21|6|7|8|3R|9|@]|A|@]|B|$]]|$2|22|4|23|6|7|8|3S|9|@]|A|@]|B|$]]|$2|24|4|12|6|7|8|3T|9|@]|A|@]|B|$]]|$2|25|4|26|6|7|8|3U|9|@]|A|@]|B|$]]|$2|27|4|28|6|7|8|3V|9|@]|A|@]|B|$]]|$2|29|4|1G|6|7|8|3W|9|@]|A|@]|B|$]]|$2|2A|4|2B|6|7|8|3X|9|@]|A|@]|B|$]]|$2|2C|4|2D|6|7|8|3Y|9|@]|A|@]|B|$]]|$2|2E|4|2F|6|7|8|3Z|9|@]|A|@]|B|$]]|$2|2G|4|2H|6|7|8|40|9|@]|A|@]|B|$]]|$2|2I|4|2J|6|7|8|41|9|@]|A|@]|B|$]]|$2|2K|4|2L|6|7|8|42|9|@]|A|@]|B|$]]|$2|2M|4|2N|6|7|8|43|9|@]|A|@]|B|$]]|$2|2O|4|-4|6|7|8|44|9|@]|A|@]|B|$]]|$2|2P|4|2Q|6|7|8|45|9|@]|A|@]|B|$]]|$2|2R|4|2S|6|7|8|46|9|@]|A|@]|B|$]]|$2|2T|4|12|6|7|8|47|9|@]|A|@]|B|$]]]]

This answer is for similar cases if the top answer by Alasdair does not help. (E.g. if the unwanted migration is created soon again with every new migration or if it is in a bigger migration that can not be reverted or the table has been removed manually.)

<blockquote>
 ...delete the migration, without creating a new migration?
</blockquote>

TL;DR: You can delete a few last reverted (confused) migrations and make a new one after fixing models. You can also use other methods to configure it to not create a table by migrate command. The last migration must be created so that it match the current models.

<hr>

Cases why anyone do not want to create a table for a Model that must exist:

A) No such table should exist in no database on no machine and no conditions

<ul>
<li>When: It is a base model created only for model inheritance of other model.</li>
<li>Solution: Set <code>class Meta: abstract = True</code></li>
</ul>

B) The table is created rarely, by something else or manually in a special way.

<ul>
<li>Solution: Use <code>class Meta: managed = False</code> 
The migration is created, but never used, only in tests. Migration file is important, otherwise database tests can't run, starting from reproducible initial state.</li>
</ul>

C) The table is used only on some machine (e.g. in development).

<ul>
<li>Solution: Move the model to a new application that is added to INSTALLED_APPS only under special conditions or use a conditional <code>class Meta: managed = some_switch</code>.</li>
</ul>

D) The project uses multiple databases in <code>settings.DATABASES</code>

<ul>
<li>Solution: Write a <a href="https://docs.djangoproject.com/en/1.11/topics/db/multi-db/#automatic-database-routing" rel="nofollow noreferrer">Database router</a> with method <code>allow_migrate</code> in order to differentiate the databases where the table should be created and where not.</li>
</ul>

<hr>

The migration is created in all cases A), B), C), D) with Django 1.9+ (and only in cases B, C, D with Django 1.8), but applied to the database only in appropriate cases or maybe never if required so. Migrations have been necessary for running tests since Django 1.8. The complete relevant current state is recorded by migrations even for models with managed=False in Django 1.9+ to be possible to create a ForeignKey between managed/unmanaged models or to can make the model managed=True later. (This question has been written at the time of Django 1.8. Everything here should be valid for versions between 1.8 to the current 2.2.)

If the last migration is (are) not easily revertible then it is possible to cautiously (after database backup) do a <a href="https://stackoverflow.com/q/46772762/448474">fake revert</a> <code>./manage.py migrate --fake my_app 0010_previous_migration</code>, delete the table manually.

If necessary, create a fixed migration from the fixed model and apply it without changing the database structure <code>./manage.py migrate --fake my_app 0011_fixed_migration</code>.

entityMap|blocks|key|8rf1j|text|如果您在恢复迁移时遇到问题，并且不知何故搞乱了迁移，您可以执行以下操作|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2gssl|迁移。|9tl09|./manage.py+migrate++--ignore-ghost-migrations+--merge+--fake|code-block|syntax|javascript|d9krt|对于|adv40|django版本低于1.7|17vj0|这将在中创建条目|acb4u|表中，您需要删除该条目。|9ijg6|现在，您将能够轻松地恢复迁移。|ds3q2|PS:我被困了很长一段时间，执行假迁移，然后恢复过来帮助我摆脱了困境。^0|0|0|0|0|0|0|0|0^^$0|$]|1|@$2|3|4|5|6|7|8|V|9|@]|A|@]|B|$]]|$2|C|4|D|6|7|8|W|9|@]|A|@]|B|$]]|$2|E|4|F|6|G|8|X|9|@]|A|@]|B|$H|I]]|$2|J|4|K|6|7|8|Y|9|@]|A|@]|B|$]]|$2|L|4|M|6|7|8|Z|9|@]|A|@]|B|$]]|$2|N|4|O|6|7|8|10|9|@]|A|@]|B|$]]|$2|P|4|Q|6|7|8|11|9|@]|A|@]|B|$]]|$2|R|4|S|6|7|8|12|9|@]|A|@]|B|$]]|$2|T|4|U|6|7|8|13|9|@]|A|@]|B|$]]]]

If you are facing trouble while reverting back the migration, and somehow have messed it, you can perform <code>fake</code> migrations.

<pre><code>./manage.py migrate &lt;name&gt; --ignore-ghost-migrations --merge --fake
</code></pre>

For django version &lt; 1.7 this will create entry in <code>south_migrationhistory</code> table, you need to delete that entry.

Now you'll be able to revert back the migration easily.

PS: I was stuck for a lot of time and performing fake migration and then reverting back helped me out.

entityMap|blocks|key|bdrdv|text|在恢复之前不要删除迁移文件。我犯了这个错误，没有迁移文件，数据库就不知道要删除什么东西。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|8tgo3|python+manage.py+showmigrations
python+manage.py+migrate+{app+name+from+show+migrations}+{00##_migration+file.py}|code-block|syntax|javascript|b7bu8|如果要恢复所有迁移|ahrf6|，使用|dev1e|作为迁移的名称：|2f10d|python+manage.py+migrate+app_name_here+zero|3v07g|删除迁移文件。一旦所需的迁移在您的模型中...|3bsaf|python+manage.py+makemigrations
python+manage.py+migrate^0|0|0|0|0|0|0|0^^$0|$]|1|@$2|3|4|5|6|7|8|T|9|@]|A|@]|B|$]]|$2|C|4|D|6|E|8|U|9|@]|A|@]|B|$F|G]]|$2|H|4|I|6|7|8|V|9|@]|A|@]|B|$]]|$2|J|4|K|6|7|8|W|9|@]|A|@]|B|$]]|$2|L|4|M|6|7|8|X|9|@]|A|@]|B|$]]|$2|N|4|O|6|E|8|Y|9|@]|A|@]|B|$F|G]]|$2|P|4|Q|6|7|8|Z|9|@]|A|@]|B|$]]|$2|R|4|S|6|E|8|10|9|@]|A|@]|B|$F|G]]]]

Don't delete the migration file until after the reversion. I made this mistake and without the migration file, the database didn't know what things to remove.
<pre><code>python manage.py showmigrations
python manage.py migrate {app name from show migrations} {00##_migration file.py}
</code></pre>
<a href="https://docs.djangoproject.com/en/3.1/topics/migrations/#reversing-migrations" rel="noreferrer">If you want to revert all migrations</a>, use <code>zero</code> as the name of the migration:
<pre><code>python manage.py migrate app_name_here zero
</code></pre>
Delete the migration file. Once the desired migration is in your models...
<pre><code>python manage.py makemigrations
python manage.py migrate
</code></pre>

entityMap|blocks|key|evogk|text|您可以通过迁移到以前的迁移来恢复。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|bid7u|例如，使用以下命令：|5kguq|./manage.py+migrate+example_app+one_left_to_the_last_migration|code-block|syntax|javascript|tht7|然后删除|1l44b|文件。^0|0|0|0|0^^$0|$]|1|@$2|3|4|5|6|7|8|N|9|@]|A|@]|B|$]]|$2|C|4|D|6|7|8|O|9|@]|A|@]|B|$]]|$2|E|4|F|6|G|8|P|9|@]|A|@]|B|$H|I]]|$2|J|4|K|6|7|8|Q|9|@]|A|@]|B|$]]|$2|L|4|M|6|7|8|R|9|@]|A|@]|B|$]]]]

You can revert by migrating to the previous migration.
For example use below command:
<pre><code>./manage.py migrate example_app one_left_to_the_last_migration
</code></pre>
then delete <code>last_migration</code> file.

entityMap|blocks|key|avpgd|text|有一个很好的库可以使用它的名为djagno-nomad，尽管与所问的问题没有直接关系，但我想分享这个，|type|unstyled|depth|inlineStyleRanges|entityRanges|data|ckdoj|场景:大多数情况下，当切换到项目时，我们认为它应该恢复我们在当前分支上所做的更改，这正是这个库所做的，请查看下面的内容|alm1p|https://pypi.org/project/django-nomad/^0|0|0^^$0|$]|1|@$2|3|4|5|6|7|8|G|9|@]|A|@]|B|$]]|$2|C|4|D|6|7|8|H|9|@]|A|@]|B|$]]|$2|E|4|F|6|7|8|I|9|@]|A|@]|B|$]]]]

there is a good library to use its called djagno-nomad, although not directly related to the question asked, thought of sharing this,
scenario: most of the time when switching to project, we feel like it should revert our changes that we did on this current branch, that's what exactly this library does, checkout below
<a href="https://pypi.org/project/django-nomad/" rel="nofollow noreferrer">https://pypi.org/project/django-nomad/</a>

entityMap|blocks|key|buhu0|text|要恢复迁移，请执行以下操作：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|86ii4|python+manage.py+migrate|code-block|syntax|javascript|dg4lt|是要恢复到的迁移的数字前缀，例如|e1dnb|转到|1ur3s|迁移。然后，您可以删除该迁移。|9aruc|您可以使用|1cpsu|作为您的迁移编号，以恢复应用程序的所有迁移。^0|0|0|0|0|0|0^^$0|$]|1|@$2|3|4|5|6|7|8|R|9|@]|A|@]|B|$]]|$2|C|4|D|6|E|8|S|9|@]|A|@]|B|$F|G]]|$2|H|4|I|6|7|8|T|9|@]|A|@]|B|$]]|$2|J|4|K|6|7|8|U|9|@]|A|@]|B|$]]|$2|L|4|M|6|7|8|V|9|@]|A|@]|B|$]]|$2|N|4|O|6|7|8|W|9|@]|A|@]|B|$]]|$2|P|4|Q|6|7|8|X|9|@]|A|@]|B|$]]]]

To revert a migration:
<pre><code>python manage.py migrate &lt;APP_NAME&gt; &lt;MIGRATION_NUMBER_PREFIX&gt;
</code></pre>
<code>MIGRATION_NUMBER_PREFIX</code> is the number prefix of the migration you want to revert to, for instance <code>0001</code> to go to <code>0001_initial.py</code> migration. then you can delete that migration.
<blockquote>
You can use <code>zero</code> as your migration number to revert all migrations of an app.
</blockquote>

I've made a migration that added a new table and want to revert it and delete the migration, without creating a new migration.

How do I do it? Is there a command to revert last migration and then I can simply delete the migration file?

How to revert the last migration?

 我进行了一次迁移，添加了一个新表，并希望恢复并删除迁移，而不创建新的迁移。 我该怎么做呢？是否有恢复上次迁移的命令，然后我可以简单地删除迁移文件？

问如何恢复上次迁移？
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问如何恢复上次迁移？EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问如何恢复上次迁移？
EN