#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):
Thanks, I'm already writing an email to akaar...@gmail.com, will await
their response.
I've been seeing some code, exactly:
https://github.com/django/django/blob/stable/1.8.x/django/db/models/sql/compiler.py
Line number: 882
return '%s.%s IN (%s)' % (qn(alias), qn2(columns[0]), sql), params
more or less there, shoulds verify that the added subquery belongs to the
same database, otherwise not allowed and should evaluate the subquery but
values.
I do not have much experience but I would like to make my first
contribution, maybe not the right place in the code to solve the problem,
but if we could you help me add the right solution.
--
Ticket URL: <https://code.djangoproject.com/ticket/25811#comment:7>
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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/064.b313e4155df56eb47cce6bc8562a2655%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
