#16713: Fixture loading for tests ignore database specific names
-------------------------------+-----------------------------------
Reporter: brent@… | Owner: nobody
Type: Bug | Status: new
Milestone: | Component: Testing framework
Version: 1.3 | Severity: Normal
Keywords: fixtures, multidb | Triage Stage: Unreviewed
Has patch: 0 | Easy pickings: 0
UI/UX: 0 |
-------------------------------+-----------------------------------
This is either a doc clarification bug, or a real bug. But based on this
from the documentation:
'''Database-specific fixtures
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.'''
This does not working during testing though. If you do not set multi_db =
True, the fixtures are loaded into 'default' only. If you do set multi_db
= True, all fixtures are loaded into all databases. There is no way to
load some data into one database and some other data into the second as
the above paragraph states.
If this is *really* a bug and just not the expected behavior and/or
someone wants the expected behavior to change I could submit a patch. But
I don't want to fix something that may not be broken.
Attached is a test project that shows the behavior.
--
Ticket URL: <https://code.djangoproject.com/ticket/16713>
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 [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.
