#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.2-alpha
Resolution: | Keywords:
Stage: Accepted | Has_patch: 0
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
----------------------------------------+-----------------------------------
Changes (by jbalogh):
* cc: jbalogh (added)
Comment:
My solution was to write a master/slave engine that doesn't depend on
having slaves: http://gist.github.com/271740. If no slaves are available,
everything goes to default. I'm pretty sure it works, but I obviously
haven't figured out how to test it automatically. ;)
One thing I discovered playing around with this: if `TEST_NAME=None`
databases are skipped during test setup, but still exist in `DATABASES`,
they'll all have to point at the same connection. If the "slave"
databases are pointing at the master, but with separate connections, the
slaves won't see anything happening in the master's transaction.
--
Ticket URL: <http://code.djangoproject.com/ticket/12542#comment:2>
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.
