Opened 22 hours ago
Last modified 22 hours ago
#36663 new Bug
Make management commands default to running checks against all databases
| Reported by: | Tim Graham | Owned by: | |
|---|---|---|---|
| Component: | Core (System checks) | Version: | dev |
| Severity: | Normal | Keywords: | |
| Cc: | Simon Charette | Triage Stage: | Accepted |
| Has patch: | yes | Needs documentation: | yes |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description
In 0b83c8cc4db95812f1e15ca19d78614e94cf38dd (refs #31055), many field checks stopped running by default (see ticket:31286#comment:10 for a long analysis), thus postponing warnings and errors that would be detected runserver or makemigrations until migrate.
As proposed by Simon in ticket:31286#comment:9, the running of these checks should be restored.
Change History (3)
comment:1 by , 22 hours ago
| Has patch: | set |
|---|---|
| Needs documentation: | set |
comment:2 by , 22 hours ago
| Cc: | added |
|---|---|
| Triage Stage: | Unreviewed → Accepted |
comment:3 by , 22 hours ago
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."
I guess we would have to go back to detecting whether or not they requested via --tag=database.
PR