#23699: Migrate in unittest still loads initial data
-------------------------------------+-------------------------------------
Reporter: tony-zhu | Owner: nobody
Type: Bug | Status: new
Component: Core (Management | Version: 1.7
commands) | Resolution:
Severity: Normal | Triage Stage:
Keywords: | Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by tony-zhu):
It is a duplicate ticket.
But the 1.7 release does break the apps which have initial_data and want
to be compatible with both Django 1.6+South and Django 1.7.
My pull request https://github.com/tony-
zhu/django/commit/f533a949af2da4d2e8a59edade03772c7b74d0a4 at least makes
the "flush" command do what it claims doing, that is only load
initial_data for unmigrated apps.
My local test shows it will keep the behavior of unmigrated app as the old
syncdb and ignore the initial_data for migrated apps. Which I think might
be a better solution for the users to adapt the new migration framework.
--
Ticket URL: <https://code.djangoproject.com/ticket/23699#comment:2>
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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/066.c98c65abac4c604ebd75ab1bbd073ca2%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
