#25172: System checks don't respect database routers
-------------------------------------+-------------------------------------
Reporter: delinhabit | Owner: nobody
Type: Bug | Status: new
Component: Core (System | Version: 1.7
checks) |
Severity: Normal | Resolution:
Keywords: system-checks | Triage Stage: Accepted
multi-database |
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by timgraham):
If it works, great! For a test, I would create a new file
`test/check_framework/test_multi_db.py` and write a custom database router
based on the default/other databases aliases so that the checks are only
run on one of the databases and then use mock to verify which connection's
validation methods are called. Let me know if you run into trouble. Not
positive that will work, but that would be the direction I'd try.
--
Ticket URL: <https://code.djangoproject.com/ticket/25172#comment:2>
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/068.5ae6709b79cf97cc625ec9c75ff6b458%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
