#30813: dumpdata > flush > loaddata.
-------------------------------------+-------------------------------------
Reporter: Maksych | Owner: nobody
Type: Bug | Status: closed
Component: Core (Management | Version: master
commands) |
Severity: Normal | Resolution: invalid
Keywords: | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by felixxm):
This is documented behavior, please take a look at
[https://docs.djangoproject.com/en/2.2/ref/django-admin/#flush flush
documentation]:
> Removes all data from the database and **re-executes any post-
synchronization handlers**. The table of which migrations have been
applied is not cleared. If you would rather start from an empty database
and re-run all migrations, **you should drop and recreate the database**
and then run migrate instead.
so `flush` removes all data from the database and **re-executes post-
synchronization handlers** which recreates `ContentType`'s with different
IDs.
--
Ticket URL: <https://code.djangoproject.com/ticket/30813#comment:3>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/065.76293f8881ddaea466469d8a9bdb0609%40djangoproject.com.
