#26683: Oracle DBs: Add option to use VARCHAR2 data type
--------------------------------+--------------------
Reporter: elarandjelovic | Owner: nobody
Type: New feature | Status: new
Component: Migrations | Version: 1.9
Severity: Normal | Keywords: Oracle
Triage Stage: Unreviewed | Has patch: 0
Easy pickings: 0 | UI/UX: 0
--------------------------------+--------------------
CharFields are currently created in Oracle databases using the NVARCHAR2
data type. If possible, we would like to have an option to use the
VARCHAR2 data type instead. This is preferable when using a Unicode
database, to avoid any performance degradation caused by data conversions
when the database contains a mix of the two types.
--
Ticket URL: <https://code.djangoproject.com/ticket/26683>
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/057.8da0d83613b3b57992807d0e2a45a3be%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
