#15926: Option to not load initial fixtures during syncdb
-------------------------------------+-------------------------------------
Reporter: msiedlarek | Owner: msiedlarek
Type: New feature | Status: new
Milestone: | Component: Core (Management
Version: 1.3 | commands)
Keywords: management syncdb | Severity: Normal
options fixtures | Triage Stage: Unreviewed
Has patch: 0 | Easy pickings: 0
-------------------------------------+-------------------------------------
There are some situation in which you may want to prevent automatic
loading of initial fixtures by `syncdb` management command. One example is
when you want to create a database schema and fill it with data from the
other database. If there were initial fixtures loaded in both databases
there probably would be some primary key conflicts raised.
There is a stealth option for that, called `load_initial_data`, and used
by testing setup, by I believe it's not fair to take away from user such a
useful one.
--
Ticket URL: <http://code.djangoproject.com/ticket/15926>
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-updates@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.
