#30424: Queries within AppConfig.ready() can cause issues with some Django db
commands
--------------------------------+--------------------------------------
Reporter: Rich Rauenzahn | Owner: nobody
Type: Uncategorized | Status: closed
Component: Uncategorized | Version: 1.11
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
--------------------------------+--------------------------------------
Changes (by Simon Charette):
* status: new => closed
* resolution: => invalid
Comment:
Performing database operations at module loading time should be avoided
and is warned against in the `ready()` documentation.
https://docs.djangoproject.com/en/2.2/ref/applications/#django.apps.AppConfig.ready
Performing such operations at `ready()` will have various side effects
that are hard to enumerate as it's unexpected and I'm not convinced
documenting this one is worthwhile.
--
Ticket URL: <https://code.djangoproject.com/ticket/30424#comment:2>
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 post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/066.78edae49d9ae707371145e48ef00f33d%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
