#17339: [nonrel] Factor out has_result into database backend
-------------------------------------+-------------------------------------
     Reporter:  jonash               |                    Owner:  nobody
         Type:  New feature          |                   Status:  new
    Component:  Database layer       |                  Version:  SVN
  (models, ORM)                      |               Resolution:
     Severity:  Normal               |             Triage Stage:  Accepted
     Keywords:  nonrel               |      Needs documentation:  0
    Has patch:  1                    |  Patch needs improvement:  0
  Needs tests:  0                    |                    UI/UX:  0
Easy pickings:  0                    |
-------------------------------------+-------------------------------------

Comment (by wkornewald):

 The reason why I only moved two lines to the compiler is that all the
 other operations are DB independent optimizations. The selected fields and
 query ordering etc need to be cleared on NoSQL, too. Only the extra mask
 is a SQL specific optimization and other DBs might use some other trick.
 Anyway,it would be easy to change the patch to also allow for overriding
 the other operations, but we should keep the current separation between
 extra mask and general optimizations because all nonrel backends only
 override the extra mask code and they shouldn't have to reimplement the
 general optimizations unnecessarily.

-- 
Ticket URL: <https://code.djangoproject.com/ticket/17339#comment:5>
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 post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Reply via email to