#25811: Error querying models in different databases in one queryset
-------------------------------------+-------------------------------------
Reporter: ebar0n | Owner: nobody
Type: Bug | Status: new
Component: Database layer | Version: 1.8
(models, ORM) |
Severity: Normal | Resolution:
Keywords: database | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by ebar0n):
Well, given the way the queryset are evaluated the only solution is to
force the evalucacion 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.
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 it or
someone else will?
Regards.
--
Ticket URL: <https://code.djangoproject.com/ticket/25811#comment:5>
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 post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/064.3c572fd0a3119d86cda6b3f816060328%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
