#20200: Oracle Inconsistencies with NVARCHAR2 and NCLOB
-------------------------------------+-------------------------------------
Reporter: deejross | Owner: nobody
Type: Bug | Status: new
Component: Database layer | Version: 1.5
(models, ORM) | Resolution:
Severity: Normal | Triage Stage:
Keywords: oracle | Unreviewed
Has patch: 1 | Needs documentation: 1
Needs tests: 1 | Patch needs improvement: 0
Easy pickings: 1 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by deejross):
* status: closed => new
* resolution: wontfix =>
Comment:
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
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.
That question also refers to these threads on the subject:
http://comments.gmane.org/gmane.comp.python.db.cx-oracle/3049
http://comments.gmane.org/gmane.comp.python.db.cx-oracle/2940
--
Ticket URL: <https://code.djangoproject.com/ticket/20200#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 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/066.1cd895bc14fe4316879fcbd08de8e348%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.
