#9136: Oracle backend: slicing is using row_number() instead of rownum
-------------------------------------------------------------------------------+
          Reporter:  Guillaume Taglang <[EMAIL PROTECTED]>  |         Owner:  
nobody
            Status:  new                                                       
|     Milestone:        
         Component:  Database layer (models, ORM)                              
|       Version:  1.0   
        Resolution:                                                            
|      Keywords:        
             Stage:  Unreviewed                                                
|     Has_patch:  1     
        Needs_docs:  0                                                         
|   Needs_tests:  0     
Needs_better_patch:  0                                                         
|  
-------------------------------------------------------------------------------+
Comment (by ikelly):

 Yeah, that database is running on an old Pentium 3 desktop, and it's
 probably horrendously misconfigured to boot -- I'm not a DBA.  I just
 tried running the same test on one of our real development databases, and
 in that scenario both methods run about 10k queries/second regardless of
 position, which probably just means that the network is now the bottleneck
 and I need to do a larger test.

-- 
Ticket URL: <http://code.djangoproject.com/ticket/9136#comment:5>
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 [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to