#26683: Oracle DBs: Add option to use VARCHAR2 data type
--------------------------------+--------------------------------------
Reporter: elarandjelovic | Owner: nobody
Type: New feature | Status: closed
Component: Migrations | Version: 1.9
Severity: Normal | Resolution: wontfix
Keywords: Oracle | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
--------------------------------+--------------------------------------
Comment (by shaib):
Personally I do not understand this:
> 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
What two types? VARCHAR2 and NVARCHAR2?
Either way, the request is for a feature at the database (rather than
field) level; I'm not sure that is the right granularity. I'm also not
sure what should happen if the proposed setting is changed on a database
which already has some fields (of the "wrong" type).
Could you please elaborate on these points?
--
Ticket URL: <https://code.djangoproject.com/ticket/26683#comment:4>
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/072.597646f174a5bb7930a9610f4fc4c0c0%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
