#23718: TEST_MIRROR setting doesn't work as expected (and has no tests)
-----------------------------------+------------------------------------
Reporter: coagulant | Owner: nobody
Type: Bug | Status: new
Component: Testing framework | Version: 1.7
Severity: Normal | Resolution:
Keywords: replica testing | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-----------------------------------+------------------------------------
Comment (by shaib):
The behavior in the bug description is sort-of expected, because of
transactions (`default` and `slave` are the same database -- in the test
project, they are defined this way even regardless of `TEST_MIRROR` -- but
accessed through different connections, and so, separate transactions).
I'm saying sort-of expected because it seems the test is running in a
transaction on `default` but not on `slave`, which is a little surprising
-- but not the problem claimed.
I don't think we want to force test-cases to run each test in transactions
on all databases -- I'm not sure that even makes sense; but we should
probably document that tests using more than one database should be
`TransactionTestCase`s.
--
Ticket URL: <https://code.djangoproject.com/ticket/23718#comment:6>
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 unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/067.fedf22e95f318b5e93a3c5de0ae1cc95%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
