#11003: Add USE INDEX, FORCE INDEX capabilities to ORM
---------------------------------------------------+------------------------
Reporter: Renato Alves | Owner: nobody
Status: new | Milestone:
Component: Database layer (models, ORM) | Version: SVN
Resolution: | Keywords: INDEX USE
FORCE
Stage: Unreviewed | Has_patch: 0
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
---------------------------------------------------+------------------------
Changes (by adamnelson):
* needs_better_patch: => 0
* needs_tests: => 0
* needs_docs: => 0
Comment:
I agree, I think a parameter should be added to QuerySet.extra()
http://docs.djangoproject.com/en/dev/ref/models/querysets/#extra-select-
none-where-none-params-none-tables-none-order-by-none-select-params-none
Maybe a key value like extra(final=None) for SQL to be appended to
whatever the generated SQL is. Of course, this would not be portable.
--
Ticket URL: <http://code.djangoproject.com/ticket/11003#comment:1>
Django <http://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 post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en
-~----------~----~----~----~------~----~------~--~---
