#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 Simon Charette):
Since da9fe5c717c179a9e881a40efd3bfe36a21bf4a6 (#20392) `TestCase`
subclasses execution is wrapped in a transaction per-db on class setup and
each method is wrapped in a save point per-db.
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 checkpoints in `TestCase.setUpClass()` and
`tearDownClass()`.
--
Ticket URL: <https://code.djangoproject.com/ticket/28263#comment:5>
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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/066.89f5a423109a833a1c4fcdf1a645c090%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
