#14610: fixtures should be able to specify their database
---------------------------------------+-----------------------------------
Reporter: cyberlogi | Owner: nobody
Type: New feature | Status: new
Milestone: | Component: Testing framework
Version: 1.2 | 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 |
---------------------------------------+-----------------------------------
Changes (by brenthoover):
* cc: brenthoover (added)
* ui_ux: => 0
Comment:
According to the docs, this feature already exists (in 1.3)
https://docs.djangoproject.com/en/1.3/ref/django-admin/#database-specific-
fixtures
'''Database-specific fixtures'''[[BR]]
''If you are in a multi-database setup, you may have fixture data that you
want to load onto one database, but not onto another. In this situation,
you can add database identifier into . If your DATABASES setting has a
'master' database defined, you can define the fixture mydata.master.json
or mydata.master.json.gz. This fixture will only be loaded if you have
specified that you want to load data onto the master database.''
So it would seem that the syntax is already prescribed for multi-db
fixtures. However, from my experience this does not work correctly, or at
least always. I found this looking for an existing bug report before
submitting one. However it is in here as a feature request and I do not
feel qualified to change it to a bug.
--
Ticket URL: <https://code.djangoproject.com/ticket/14610#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 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.
