Changes between Initial Version and Version 1 of Ticket #20200, comment 5


Ignore:
Timestamp:
01/27/2014 01:33:55 PM (16 months ago)
Author:
deejross
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #20200, comment 5

    initial v1  
    1 I never got any notifications on responses from this, so I'm sorry for not getting back to you. Here's the perfect reason why N-type fields should not be used with Oracle and Django: http://stackoverflow.com/questions/18978536/poor-performance-of-django-orm-with-oracle
    2 
    3 We are at the tail end of the conversion process from MySQL or Oracle, and I had noticed a severe performance problem with Oracle. It turns out there are cases where Oracle's implicit type conversion rules prevent indexes from being used sometimes. This means full table scans, regardless of your indexes. The only workaround is to use cursor.execute() or to create a C2C index on every field, neither of which are suitable options.
    4 
    5 That question also refers to these threads on the subject:
    6 http://comments.gmane.org/gmane.comp.python.db.cx-oracle/3049
    7 http://comments.gmane.org/gmane.comp.python.db.cx-oracle/2940
     1Disregard, a seperate bug report will be filed.
Back to Top