#15578: loaddata and processing order of fixtures
---------------------------+---------------------------
Reporter: lsaffre | Owner: nobody
Status: new | Milestone:
Component: Uncategorized | Version: 1.2
Keywords: | Triage Stage: Unreviewed
Has patch: 0 |
---------------------------+---------------------------
As the documentation for loaddata correctly says: "the order in which
fixture files are processed is undefined."
That's a pity because I use fixtures to provide combinable and
interdependent sets of demo data.
Would it be difficult to implement a rule for the order in which fixtures
are loaded?
I'd suggest the following rule:
If there are 3 applications "a", "b" and "c" and you invoke
{{{
manage.py loaddata foo bar baz
}}}
(or you specify
{{{
fixtures = ['foo','bar','baz']
}}}
in a TestCase, then loaddata would first load all fixtures 'foo' for all
applications, then all fixtures named 'bar', then all fixtures 'baz'.
--
Ticket URL: <http://code.djangoproject.com/ticket/15578>
Django <http://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 post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en.
