#25811: Error querying models in different databases in one queryset
-------------------------------------+-------------------------------------
Reporter: ebar0n | Owner: nobody
Type: | Status: new
Cleanup/optimization |
Component: Database layer | Version: master
(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):
Thanks for the clarification, I fully understand the performance problems
that this may cause, but because I'm pretty sure that when a developer
decides to use different database and do this kind of consultation should
take into account this potential problem (if you have a subquery with
thousands of records), if it continues in the same database which is
running as the subquery is generating optimally. Also in the official
documentation shall specify the variant behavior.
But then I respect their opinions; I will correct the code to add the
exception as suggested, so that other users do not fall into the same
error time and tarden known to occur. and only I customize my code.
Thank you for your help.
--
Ticket URL: <https://code.djangoproject.com/ticket/25811#comment:14>
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.137da088e570248c8b7c625af5d4c766%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
