  Squashes the migrations for \fBapp_label\fP up to and including \fBmigration_name\fP
  down into fewer migrations, if possible. The resulting squashed migrations
  can live alongside the unsquashed ones safely. For more information,
  please read migration\-squashing\&.
  .sp
  
  .sp
  When \fBstart_migration_name\fP is given, Django will only include migrations
  starting from and including this migration. This helps to mitigate the
  squashing limitation of \fBRunPython\fP and
  \fBdjango.db.migrations.operations.RunSQL\fP migration operations.
 
</s> remove .B django\-admin squashmigrations
 </s> add .B django\-admin squashmigrations app_label [start_migration_name] migration_name </s> remove By default, Django will try to optimize the operations in your migrations
to reduce the size of the resulting file. Pass \fB\-\-no\-optimize\fP if this
process is failing for you or creating incorrect migrations, though please
also file a Django bug report about the behavior, as optimization is meant
to be safe.
.SS startapp <app_label> [destination]
 </s> add Disables the optimizer when generating a squashed migration. By default, Django
will try to optimize the operations in your migrations to reduce the size of
the resulting file. Use this option if this process is failing or creating
incorrect migrations, though please also file a Django bug report about the
behavior, as optimization is meant to be safe. </s> remove 
.sp
The \fB\-\-keepdb\fP option can be used to preserve the test database between test
runs. This has the advantage of skipping both the create and destroy actions
which can greatly decrease the time to run tests, especially those in a large
test suite. If the test database does not exist, it will be created on the first
run and then preserved for each subsequent run. Any unapplied migrations will also
be applied to the test database before running the test suite.
 </s> add Preserves the test database between test runs. This has the advantage of
skipping both the create and destroy actions which can greatly decrease the
time to run tests, especially those in a large test suite. If the test database
does not exist, it will be created on the first run and then preserved for each
subsequent run. Any unapplied migrations will also be applied to the test
database before running the test suite. </s> remove .B \-\-reverse
 </s> add .B \-\-reverse, \-r </s> remove The \fI\%\-\-database\fP option can be used to specify the database
onto which the cache table will be installed, but since this information is
pulled from your settings by default, it\(aqs typically not needed.
.sp
The \fI\%\-\-dry\-run\fP option will print the SQL that would be run without
actually running it, so you can customize it or use the migrations framework.
 </s> add Specifies the database in which the cache table(s) will be created. Defaults to
\fBdefault\fP\&.
.INDENT 0.0
.TP
.B \-\-dry\-run
.UNINDENT
  Squashes the migrations for \fBapp_label\fP up to and including \fBmigration_name\fP
  down into fewer migrations, if possible. The resulting squashed migrations
  can live alongside the unsquashed ones safely. For more information,
  please read migration\-squashing\&.


  .sp
  When \fBstart_migration_name\fP is given, Django will only include migrations
  starting from and including this migration. This helps to mitigate the
  squashing limitation of \fBRunPython\fP and
  \fBdjango.db.migrations.operations.RunSQL\fP migration operations.
keep keep keep keep replace replace keep keep keep keep keep
 Updated man page for Django 2.0 alpha. 
docs/man/django-admin.1