Hi! I implemented FilteredRawQuerySet which supports filter() and order_by() like model manager QuerySet.
https://code.djangoproject.com/ticket/28087 https://github.com/Dmitri-Sintsov/django-jinja-knockout/blob/master/django_jinja_knockout/query.py Internally it contains RawQuerySet and QuerySet for the target model. SELECT part of the query is borrowed from RawQuerySet, while WHERE and ORDER BY statements are generated via QuerySet query. This feature is useful when the code uses programmatically generated arguments of filter() / order_by(), for example in class-based ListView with custom filtering and / or sorting. Is such feature worth to be included to Django core? I could just continue to use my own implementation (probably imperfect) however I am worrying about possible query generation code changes that could make my module incompatible in the future. In case such queryset would be included to Django code, there are much more chances that the code which uses it would not break when updating to newer Django version. Dmitriy -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. Visit this group at https://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/a20e043e-aec8-4806-9e6b-c5c669361c44%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
