#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):
With regards to the slow queries it was VARCHAR2 to NVARCHAR2 translation
that was the killer, one table had around 100 million rows, and was
executing as a full table scan, so understandably took a while.
I agree with and understand all of your points. It's a complex situation
and there doesn't appear to be a simple solution.
My recommendation would be to create a new backend with the desired
behaviour, and mark the current one as deprecated in version x.x.x
Then in version x.x.x+1, switch to having the new backend as the default
and drop support for the older one. Migration can be done at the Python
level as you suggested, or alternatively there is this tool from Oracle
that any dba (or even dev) can use to convert the DB to unicode. Literally
just need to click a few buttons then wait a while for it to convert.
{{{
http://www.oracle.com/technetwork/database/database-
technologies/globalization/dmu/overview/index.html
}}}
There will be some initial pain for sites using the legacy approach, but I
think in the long run this will benefit the Django project, and in turn
the community.
--
Ticket URL: <https://code.djangoproject.com/ticket/26683#comment:8>
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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/072.5ee1b26681c777046df55c897636496d%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
