Context Navigation

Changes between Initial Version and Version 1 of Ticket #31286, comment 9

initial	v1
12	12	> Although it's documented that "Database checks are not run by default because they do more than static code analysis as regular checks do," the database-specific field checks are only static analysis (as opposed to something like the MySQL check for strict mode which does query the database), so I see no reason they shouldn't be included as part of the normal checks.
13	13
14		I don't disagree in principle but that seems like a totally different can of worm isn't it? Database checks [https://github.com/django/django/commit/0b83c8cc4db95812f1e15ca19d78614e94cf38dd#diff-f10ce154e1f5bcdba92b54ebf8cb57357b404a3f03ab51ca85a031358f7372ecL66-L69 were never ran by default even prior to this patch] so it has little to do this with this particular ticket.
	14	I don't disagree in principle but that seems like a totally different can of worm isn't it? Database checks [https://github.com/django/django/commit/0b83c8cc4db95812f1e15ca19d78614e94cf38dd#diff-f10ce154e1f5bcdba92b54ebf8cb57357b404a3f03ab51ca85a031358f7372ecL66-L69 were never ran by default even prior to this patch] so it has little to do this with this particular ticket beyond the fact that specifying a `--database` is now the opt-in for enabling those instead of `--tag database`.