#30713: ListView queryset issue
-------------------------------------+-------------------------------------
Reporter: Dmitrij | Owner: nobody
Strelnikov |
Type: Bug | Status: new
Component: Database | Version: 2.2
layer (models, ORM) |
Severity: Normal | Keywords: queryset
Triage Stage: | Has patch: 0
Unreviewed |
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 | Easy pickings: 0
UI/UX: 0 |
-------------------------------------+-------------------------------------
Hi guys,
is this intentional behaviour or not?
{{{
class SomeQuerySet(models.QuerySet):
def active(self):
print('active')
data = cache.get(CACHE_KEY)
if data is None:
print('no cache')
data =
self.select_related('related').filter(date_expired__gte=timezone.localtime().now()).filter(
some__is_active=True).order_by('-date_activated')
cache.set(CACHE_KEY, data, 30)
return data
}}}
{{{
class QSSomeListView(ListView):
queryset = Some.objects.active()
}}}
{{{
class GetQSSomeListView(ListView):
def get_queryset(self):
return Some.objects.active()
}}}
QSSomeListView never print anything from `active()` method on page access,
and actually never hit cache. It print only `active` once at project
startup.
GetQSSomeListView works as expected.
If its intentional, could you please explain / point me why so?
Thank you.
--
Ticket URL: <https://code.djangoproject.com/ticket/30713>
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 on the web visit
https://groups.google.com/d/msgid/django-updates/053.8f38a77d6091772e093d82595ec6ddda%40djangoproject.com.
