#26273: Module level queries in a project can crash migrations if the queried
model
schema changed.
-------------------------------------+-------------------------------------
Reporter: scoenye | Owner: nobody
Type: Bug | Status: closed
Component: Uncategorized | Version: 1.9
Severity: Normal | Resolution: invalid
Keywords: classmethod | Triage Stage:
queryset manage.py | Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by timgraham):
* status: new => closed
* resolution: => invalid
Comment:
I started [https://groups.google.com/d/topic/django-
developers/7JwWatLfP44/discussion a discussion on django-developers] based
on Simon's proposal to add a warning or prohibit module level queries.
Let's open a new ticket with action items based on the results.
--
Ticket URL: <https://code.djangoproject.com/ticket/26273#comment:3>
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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/065.f6086d6edcfb18ab48134ea4f0678092%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
