#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
-----------------------------------+------------------------------------
Comment (by shai):
The Oracle backend supports a test parameter `CREATE_DB` that tells it not
to create the (tablespace, in this context equivalent to database) for
testing but rather use an existing one. It still tries to create tables,
but I guess the `managed=False` setting would take care of that in this
context.
I would like to make that parameter apply to all database backends.
--
Ticket URL: <https://code.djangoproject.com/ticket/14296#comment:11>
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.b33f1c32db777cb0f0289557c3fd240f%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
