#12542: Test framework needs a way to restrict the number of databases created
in a
multi-db setup
-------------------------------+--------------------------------------------
Reporter: russellm | Owner: nobody
Status: new | Milestone:
Component: Testing framework | Version: 1.1
Keywords: | Stage: Unreviewed
Has_patch: 0 |
-------------------------------+--------------------------------------------
Brett Hoerner [http://groups.google.com/group/django-
developers/browse_thread/thread/286cc88ad9953df4 raised an interesting
point on django-dev] about testing under multi-db:
If you have a master/slave setup, your DATABASES setup will describe
multiple databases, but unless you're actually testing the master/slave
setup, you don't need multiple databases to test general application logic
- you just need a single data source.
Django should provide a way to say "only sync this subset of databases
during testing".
The initial suggestion is to allow TEST_NAME=None to be interepreted as
"don't create this database under testing".
--
Ticket URL: <http://code.djangoproject.com/ticket/12542>
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.
