#14296: 'manage.py test' failing for apps that access read-only databases
-----------------------------------+-------------------------------------
Reporter: kthhrv | Owner: nobody
Type: Bug | Status: closed
Component: Testing framework | Version: 1.2
Severity: Normal | Resolution: needsinfo
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-----------------------------------+-------------------------------------
Changes (by shaib):
* status: new => closed
* cc: shaib (added)
* resolution: => needsinfo
Comment:
6 years after a general workaround was suggested, and almost two years
since the last comment, I think that anybody who wants improvement on this
should specify exactly what they need and why.
In particular -- the combination of `--keepdb` and database routers
disallowing migrations on the read-only database will stop any automatic
schema changes, and using Luke's suggestions for test-cases should stop
data changes as well.
--
Ticket URL: <https://code.djangoproject.com/ticket/14296#comment:13>
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/064.cb62f1d094096f72da23846dacc4587a%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
