#36739: `manage.py check` unexpectedly accesses database when JSONField is used
-------------------------------------+-------------------------------------
Reporter: Storm Heg | Owner: (none)
Type: Bug | Status: closed
Component: Core (System | Version: dev
checks) |
Severity: Normal | Resolution: invalid
Keywords: | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Storm Heg):
Thanks for the quick responses.
I suspected this might have been intentional, but wanted to make sure.
Happy to close 👍
@Jacob what kind of wording would you like to see in the release notes?
I was looking in the documentation for system checks for a good place to
document this behavior / expectation so this does not stay undocumented,
but I'm not sure of a good place this would fit. Currently, the
`databases` section
(https://github.com/django/django/blob/0c487aa3a7b2417481bf48c1e5355c855873e210/docs/ref/checks.txt#L81)
reads `Database checks are not run by default because they do more than
static code analysis as regular checks do` which implies regular checks
only do static analysis (which turns out to not necessarily be true).
Seems like low hanging fruit for a small docs improvement too.
--
Ticket URL: <https://code.djangoproject.com/ticket/36739#comment:5>
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/0107019a92544362-dbbd30f9-a1bc-448c-a880-65a121ec5a4f-000000%40eu-central-1.amazonses.com.
