#14296: 'manage.py test' failing for apps that access read-only databases
-----------------------------------+------------------------------------
Reporter: kthhrv | Owner: nobody
Type: Bug | Status: new
Component: Testing framework | Version: 1.2
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
-----------------------------------+------------------------------------
Changes (by gchp):
* cc: gregchapple1@… (added)
Comment:
As of b7aa7c4ab4372d2b7994d252c8bc87f77dd217ae you can use the `--keepdb`
parameter to use an existing database rather than creating a new one for
testing. This sounds more or less like what shai is describing above. It
will run any outstanding migrations, and flush the data, but ultimately
the database will be preserved at the end of the run.
--
Ticket URL: <https://code.djangoproject.com/ticket/14296#comment:12>
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.f4437495645624ac22cc01267b9d0da2%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
