#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: 1
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Simon Charette):
Thanks for the assignment Jacob and sorry for not doing it myself.
> Simon, do you feel we shoul try to maintain the behavior: "Database
checks are not run by default because they do more than static code
analysis as regular checks do. They are only run by the migrate command or
if you specify configured database aliases using the --database option
when calling the check command."
Tim, I don't have a strong opinion here, I'm slightly in favor of not
special casing database checks but I think it's a distinct problem that
would warrant a larger discussion. Do you have any objection on keeping
this ticket focused on making sure that when database checks are run they
default to all databases?
Any thoughts on the PR so far?
--
Ticket URL: <https://code.djangoproject.com/ticket/36663#comment:6>
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/0107019a1d128589-09b610f7-8527-45ce-888c-289a38b72a17-000000%40eu-central-1.amazonses.com.
