#13128: Fixture docs could be more clear.
------------------------------------+---------------------------------------
Reporter: orokusaki | Owner: nobody
Status: new | Milestone:
Component: Documentation | Version: SVN
Keywords: fixtures, initial_data | Stage: Unreviewed
Has_patch: 0 |
------------------------------------+---------------------------------------
At http://docs.djangoproject.com/en/dev/howto/initial-data/#automatically-
loading-initial-data-fixtures
The docs mention creating initial_data.[format], etc for auto-popping data
during {{{manage.py syncdb}}}. The docs don't make mention of where to
place this file. If they can go anywhere it might be better to mention
that, as well as mention where the search begins. I would want to put it
there, for convention, and efficiency (if it makes a difference for
speed).
On a related note,the {{{manage.py loaddata fixturename}}} appears (I
haven't used it yet) to be able to accept multiple files. This might be
useful in separating fixtures by application. The {{{initial_data}}}, on
cursory glance, doesn't appear from the docs to work this way. Having not
used either method, I would be at the mercy of trial and error to see if
this is correct. It might be good to mention in both versions (loaddata,
and the initial_data version) if you can have multiple fixture files,
whether they can exist anywhere, and where they might be best placed.
--
Ticket URL: <http://code.djangoproject.com/ticket/13128>
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 django-upda...@googlegroups.com.
To unsubscribe from this group, send email to
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en.
