#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 Jacob Walls):
Good point, we should weasel-ify that existing wording: "because they
*typically*" or "because they *can be expected to*" etc
> @Jacob what kind of wording would you like to see in the release notes?
Under "Backwards incompatible changes in 6.1" > "System checks" a sentence
about how system checks now supply all `databases` if not specified, so
calling code should be prepared for databases to potentially be accessed.
Maybe a link to the docs for the `databases` kwarg:
https://docs.djangoproject.com/en/stable/topics/checks/#writing-your-own-
checks
Thanks.
--
Ticket URL: <https://code.djangoproject.com/ticket/36739#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/0107019a9269c97d-4612d434-eca9-41f8-b067-520f2d7186bd-000000%40eu-central-1.amazonses.com.
