#23031: Django 1.7.x test failing for application with migrations and initial
data
----------------------------+------------------------------------
Reporter: linovia | Owner: nobody
Type: Bug | Status: new
Component: Migrations | Version: 1.7-rc-1
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
----------------------------+------------------------------------
Comment (by linovia):
Thinking a bit more about this, I should probably close this bug and open
a new one stating that flush command should not install initial_data for
application that have migrations.
I created a dummy project (one app with a model and initial data) and
here's what flush gives:
{{{
(django17_test) air-de-xavier:demo xordoquy$ python manage.py flush
You have requested a flush of the database.
This will IRREVERSIBLY DESTROY all data currently in the
'/Users/xordoquy/django17_test/demo/db.sqlite3' database,
and return each table to an empty state.
Are you sure you want to do this?
Type 'yes' to continue, or 'no' to cancel: yes
Installed 1 object(s) from 1 fixture(s)
}}}
If Django doesn't install initial_data for apps with migrations then we
have a bug in the flush command - which is called by the tests.
--
Ticket URL: <https://code.djangoproject.com/ticket/23031#comment:4>
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/065.828227780ae7e5879167871cf38aa38f%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
