#28263: TestCase breaks for databases that don't support savepoints
-----------------------------------+------------------------------------
Reporter: Lokesh Dokara | Owner: nobody
Type: Bug | Status: new
Component: Testing framework | Version: 1.11
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-----------------------------------+------------------------------------
Comment (by Lokesh Dokara):
Replying to [comment:5 Simon Charette]:
I think we might also need to modify `_should_reload_connections()`,
`_fixture_setup()`, `_fixture_teardown()` to achieve that.
> In your case I think you'd want to disable the transaction wrapping at
the class level so test method get wrapped in a transaction instead of
save points. I think you should be able to achieve that by also checking
that all connections support save points in `TestCase.setUpClass()` and
`tearDownClass()`.
--
Ticket URL: <https://code.djangoproject.com/ticket/28263#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/066.403e04bd99f3381cb3d98b7f94e68ed0%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
