#36663: Make management commands default to running checks against all databases
-------------------------------------+-------------------------------------
Reporter: Tim Graham | Owner: Simon
| Charette
Type: Bug | Status: assigned
Component: Core (System | Version: dev
checks) |
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Simon Charette):
* needs_docs: 1 => 0
Comment:
Thinking more about this I ended up adjusting the PR slightly so it
continues to **not run database tagged checks by default** but passes
`databases` for all databases unless restricted with `--database` in
`check` and `migrate`. I extended our regression test coverage to make
sure these any change in this regards is explicit (as my initial draft
inadvertently changed that).
As discussed above changing how databases tagged checks should be run
should be discussed somewhere else as this ticket only ensures `databases`
passing works the way it should have when we implemented #31055.
Given the change is pretty internal and a bugfix I don't think it warrants
documentation but I'm happy to include some in the release notes if you
believe otherwise.
--
Ticket URL: <https://code.djangoproject.com/ticket/36663#comment:9>
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 [email protected].
To view this discussion visit
https://groups.google.com/d/msgid/django-updates/0107019a65580155-573e774f-73bf-4f61-845b-e9024310919e-000000%40eu-central-1.amazonses.com.
