#25265: DB Backend cannot specify query class.
-------------------------------------+-------------------------------------
Reporter: techdragon | Owner: nobody
Type: New feature | Status: new
Component: Database layer | Version: master
(models, ORM) |
Severity: Normal | Resolution:
Keywords: | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by akaariai):
* needs_better_patch: => 0
* needs_tests: => 0
* needs_docs: => 0
Comment:
The problem is that QuerySets aren't tied to any given backend. What
should happen if you have two backends, one for mongodb and other for
postgres, and the user does User.objects.filter(id=10).using('postgres')?
Maybe this could be an error?
I'm not sure what we could do to help nonsql backends. Some sort of
User.objects.all() returns nonsql QuerySet seems like a possible addition,
but I'm not sure what that mechanism should be.
--
Ticket URL: <https://code.djangoproject.com/ticket/25265#comment:1>
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/068.e6d4818c4fe193a195685d89715fa941%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
