#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: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by jarshwah):
* stage: Unreviewed => Accepted
Comment:
I'm not sure what the solution to this problem is, but after discussing it
at pycon with techdragon I agree that it'd be a nice thing to fix.
Here's a couple of things off the top of my head:
1) Meta option per model: Meta: query_backend =
'django.db.models.sql.query'
2) A DATABASES option
3) A new queryset method
`Model.objects.with('django.db.models.sql.query')`
But I also think that we need to define the API between queryset and
query, so that actually writing different query backends is realistic. Not
a requirement for a solution here though.
--
Ticket URL: <https://code.djangoproject.com/ticket/25265#comment:2>
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/068.891587c0ef628502639363b16f40028e%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
