Changes between Version 2 and Version 3 of Ticket #25811, comment 5
- Timestamp:
- Nov 25, 2015, 12:45:25 PM (9 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #25811, comment 5
v2 v3 1 1 Well, given the way the queryset are evaluated the only solution is to force the evaluation of internal consultation, exactly as specified above with "list ()", but what happens when large projects where time is it separate the database ?, possibly like me exist any code with nested queries, Django should be able to generate differences that and not only evaluate the subquery separately. 2 2 3 I like it try to force this behavior, I have some experience using Django but still not at such a high level, but with some tutoring in things that maybe do not understand well make it, you think? I try to fix itor someone else will?3 I like it try to force this behavior, I have some experience using Django but still not at such a high level, but with some tutoring in things that maybe do not understand well make it, you think? I would try to fix or someone else will? 4 4 5 5 Excuse my bad English.