#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 | Resolution:
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 VackarAfzal):
Replying to [comment:10 jtiai]:
> Oracle database encoding is slightly problematic case since once you
have set it it's quite impossible to change it without reinstalling whole
server.
I can only speak for Oracle12c, but you can change the charecterset
without having to re-install the server, not sure what the situation is
with older versions.
>
> At least we and our customers do have servers that run with WE8ISO8859P1
encoding, and very probably will have them for next few years at least.
From my perspective I would like to have that datatype switch to be
permanent so I could use that per customer basis.
>
> It's not that we could use tools like DMU. It's just that some of our
customers do still have non-unicode aware applications that requires
VARCHAR2 to be something else but unicode.
>
> I could do Proof of Concept with a switch and to see if it wouldn't be
too complex to achieve.
>
> Sidenote: There is also in use NCLOB which supposed to be CLOB as well?
I've never had a use case that required NCLOB, but I'm sure there will be
others who do. Suppose it makes sense for the same reason NVARCHAR2 was
used.
--
Ticket URL: <https://code.djangoproject.com/ticket/26683#comment:12>
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.dab689cce9067d418c1cce71953072d0%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
