Test framework needs a way to restrict the number of databases created in a multi-db setup
|Reported by:||Russell Keith-Magee||Owned by:||nobody|
|Cc:||Jeff Balogh||Triage Stage:||Accepted|
|Has patch:||no||Needs documentation:||no|
|Needs tests:||no||Patch needs improvement:||no|
Brett Hoerner 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".
Change History (4)
comment:1 Changed 7 years ago by
|Patch needs improvement:||unset|
|Triage Stage:||Unreviewed → Accepted|
|Version:||1.1 → 1.2-alpha|