Re: The blacklist / master issue

I would like to share this article which has pretty compelling arguments, especially regarding the feelings (point 4). On Monday, 15 June 2020 19:28:23 UTC+3, Tom Carrick wrote: > > This ticket was closed wontfix >

Re: Subquery join support

to move this forward. https://github.com/tatarinov1997/django/pull/1/ Cheers, Alexandr. On Sunday, 12 April 2020 19:35:55 UTC+3, Alexandr Tatarinov wrote: > > Hello everyone. > So far, I've managed to implement joins via Subquery and OuterRef with > some caveats. > > To begin w

Re: Subquery join support

he reasons why the string fields and *F* expressions are treated separately and differently in various QuerySet methods are still unclear for me. The *F *expression works because the implementation relies on *Query.resolve_ref *to be called to short-circuit columns from the joined subqueri

Re: Subquery join support

Thanks, folks, that's a very valuable insight. I really love the idea of resolving *OuterRef* via .*join()*, it may help overcome problems I had with reusing *Subquery*. However, I believe *Subquery* exists apart from *QuerySet* for a reason - to separate responsibilities, so should we mix

Re: Subquery join support

Accidentally removed gist, new one is here https://gist.github.com/tatarinov1997/068fe786366401ed640dcbbbe5d959e4 On Monday, 6 April 2020 16:34:55 UTC+3, Alexandr Tatarinov wrote: > > Hello folks, > > Following the discussion > https://groups.google.com/forum/#!topic/dj

Subquery join support

Hello folks, Following the discussion https://groups.google.com/forum/#!topic/django-developers/b370mxfKCHg, I would like to suggest adding the ability to join QuerySet with a subquery clause to Django. The benefits are pretty much described and discussed in the linked topic, the only one I