  .sp
  Removes all data from the database and re\-executes any post\-synchronization
  handlers. The table of which migrations have been applied is not cleared.
  .sp
  If you would rather start from an empty database and re\-run all migrations, you
  should drop and recreate the database and then run \fI\%migrate\fP instead.
  .INDENT 0.0
  .TP
  .B \-\-noinput, \-\-no\-input
  .UNINDENT
 
</s> remove For example, if your \fBDATABASES\fP setting has a \(aqmaster\(aq database
defined, name the fixture \fBmydata.master.json\fP or
\fBmydata.master.json.gz\fP and the fixture will only be loaded when you
specify you want to load data into the \fBmaster\fP database.
 </s> add For example, if your \fBDATABASES\fP setting has a \(aqusers\(aq database
defined, name the fixture \fBmydata.users.json\fP or
\fBmydata.users.json.gz\fP and the fixture will only be loaded when you
specify you want to load data into the \fBusers\fP database. </s> remove .sp
Support for XZ archives (\fB\&.xz\fP) and LZMA archives (\fB\&.lzma\fP) was added.

 </s> add  </s> remove .sp

 </s> add  </s> remove .sp

 </s> add  </s> remove Support for calling \fBmakemigrations\fP without an active database
connection was added. In that case, check for a consistent migration
history is skipped.
 </s> add 
If you would rather start from an empty database and rerun all migrations, you
  .sp
  Removes all data from the database and re\-executes any post\-synchronization
  handlers. The table of which migrations have been applied is not cleared.
  .sp
If you would rather start from an empty database and rerun all migrations, you
  should drop and recreate the database and then run \fI\%migrate\fP instead.
  .INDENT 0.0
  .TP
  .B \-\-noinput, \-\-no\-input
  .UNINDENT
keep keep keep keep replace keep keep keep keep keep
 Updated man page for Django 4.1 alpha. 
docs/man/django-admin.1