#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 RK):
What about if it were possible to specify in the database parameters that
the test runner should create the test databases using a different
database server config entirely? Eg:
{{{
DATABASES = {
'default': {
'ENGINE': 'django.db.backends.mysql',
'NAME': 'myproject',
'HOST': 'maindb',
# ... plus some other settings
},
'readonly': {
'ENGINE': 'django.db.backends.mysql',
'NAME': 'myproject',
'HOST': 'readonlydb',
'TEST_DATABASE': 'default'
# ... plus some other settings
}
}
}}}
This would trigger the test runner to create another test database on the
"default" server, for use with anything during the test which tries to
access the "readonly" database.
--
Ticket URL: <https://code.djangoproject.com/ticket/14296#comment:10>
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.81d97fd9e442a21b4ced6b8bf67e8971%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.
